Robert Roessler: > I had a need for a "mini properties database" in an app which is using > Scintilla, and decided that the Scintilla one is up to the task - > especially with its macro expansion/replacement capabilities. :)
I'm still undecided about this so don't want to ask you to do more work yet, but ... > SCI_GETPROPERTYEXPANDED(const char *key, char *value) > > Functions the same as SCI_GETPROPERTY, except that the returned string > will have all defined macro expansion/replacement performed. This needs to say what macros look like. > A note on my implementation: as Scintilla currently classifies > SCI_SETPROPERTY as one of the functions conditionally included by > SCI_LEXER, I have added the above three functions to this same > grouping. But given that [at least] I see these as being useful > independent of lexers, one (i.e., Neil) might want to consider moving > all FOUR of the Scintilla "properties" functions out of this grouping > - or not. The SCI_LEXER variant is the big fat Scintilla which resource-constrained applications can choose not to enable. APIs should be defined in Scintilla.iface. Neil _______________________________________________ Scintilla-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scintilla-interest
