Sat Jul 11 15:11:22 CEST 2009
It looks like the simplest approach is going to be to use the _same_
language for all chips involved, which means that the set of macros
are shared. However, each chip should have its own _dictionary_.
It is ok for one or more chips in the chain to use a _different_
language, as long as it is turned off.
Now.. Maybe it's better to make sure that this isn't necessary: to be
able to use one language per host, and simply share the macro
namespaces if necessary.