>Undocumented side effect using []? Too bad, I feel now I should include places I used [] as potential bug sources:(

I like the behaviour, since it makes it possible to live without doubled defines if you need to build up object paths as strings to feed into eval() or to pass as parameters.

Otherwise the header files grow like:

* global App Obj
#DEFINE REF_APP					GoApp
#DEFINE REF_APP_STRING				"GoApp"

* Reference into Kontext Cache on Loader
#define REF_CACHE				REF_APP.Kontext_Cache
#define REF_CACHE_STRING			REF_APP_STRING + ".Kontext_Cache"

* Or even worse coding practice
#DEFINE REF_KEY					GoApp.oglKey
#DEFINE REF_KEY_STRING				"GoApp.oglKey" 

Using [] can eliminate all xxx_STRING defines. Cuts both ways <g>.

regards

thomas