Neil Hodgson wrote:

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 ...

Perhaps I misconstrued your previous reply to me?

"If you really want to do this and there is no large increase in code then it can go in due to symmetry."

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.

Since they are using Scintilla's existing "properties" facility, they look exactly like... Scintilla property macros - perhaps we are just having a naming-based confusion here (given that you do not use the word "macro" for this replacement operation)?

In any case, they are defined in the documentation for the current SCI_SETPROPERTY function... and at such time as these new calls become "standard" in Scintilla, I will add the appropriate text to ScintillaDoc.html... as I have for most (all?) of the features/changes implemented or requested by me to date - although the site is not being updated to reflect said changes. :)

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.

As you would say, "OK".

   APIs should be defined in Scintilla.iface.

I have added an updated Scintilla.iface to the getprops.zip on my site. I am a little unsure about the get/fun usage here - I used get, but maybe these should use fun?

Robert Roessler
[EMAIL PROTECTED]
http://www.rftp.com
_______________________________________________
Scintilla-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scintilla-interest

Reply via email to