David Kastrup <[email protected]> writes: >>> That might make it nicer to store the information elsewhere, such as >>> a property or hash list. But then it is getting used in core >>> functions making use of those data structures, and having another >>> non-trivial lookup per element is undesirable. So placing this >>> information along with the rest seems desirable. >> >> Another reason for not using a separate data structure is that this >> would force a separation for adding a macro/env and declaring it >> "expert". > > Isn't that more of an advantage? Makes it easier to update an existing > or autogenerated package with the expert information without having to > edit the innards of data structures/calls.
If you say it this way, then yes. ;-) First, I've thought it wouldn't make a difference as long as we provide some TeX-declare-expert function. But then I realized that if that function would modify entries in `TeX-symbol-list' and `LaTeX-environment-list' directly, the style whose entries are to be modified needs to be loaded beforehand. Bye, Tassilo _______________________________________________ auctex-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/auctex-devel
