It looks to me (based on empirical observations) that when Leo sees a
sentinel of the form
@key value
that there are two cases:
A) key is a recognized property name, in which case (assuming a Python
source)
#@@key value
is written during the tangling process
B) key is not a recognized property name, in which case
@key value
is written directly during the tangling process.
I have two questions. First, do I understand this correctly? Second,
is there a reason why it is done this way, instead of treating all
sentinels that take the form "@key value" the same regardless of whether
"key" is a recognized property name or not? I ask because as I have
mentioned before I am designing a Java/Scala DOM based on the Leo model,
and while reflecting on this I have come to the conclusion that it would
make a lot of sense to not have the recognized property names be
something that is hard-coded so that extensions can make up their own
user-specifiable properties without modifying the core classes.
Cheers,
Greg
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
