From 2ca29bdfede4a037e23f3aa567b0d3c73d19cb23 Mon Sep 17 00:00:00 2001 From: brettlangdon Date: Mon, 22 Jun 2015 07:00:41 -0400 Subject: [PATCH] remove note about references --- forge.go | 18 ------------------ 1 file changed, 18 deletions(-) diff --git a/forge.go b/forge.go index c5a3ab1..5e4d284 100644 --- a/forge.go +++ b/forge.go @@ -79,24 +79,6 @@ // statement is defined. Includes are in the format 'include "";'. The can be any glob // like pattern which is compatible with `path.filepath.Match` http://golang.org/pkg/path/filepath/#Match // -// Note about references. -// -// References are resolved during parsing not access (they do not act as pointers... today). -// Meaning that if I have the following config: -// setting = "value"; -// ref_to_setting = setting; -// -// During parsing when I get to `ref_to_setting` it will be resolved immediately and it's value will -// be set to `"value"`. -// -// This config example, however, will raise a parsing error since it cannot resolve the reference: -// ref_to_setting = setting; -// setting = "value"; -// -// Since `setting` does not exist yet. -// This is mostly due to the naive implementation of references today. How they work may change in -// future versions or they may disappear entirely. -// package forge import (