1. Modifying entry sizes in eu.ex
Hi the list!
I started fiddling with the 2.5 source and got two useful
features implemented so far:
1/
choose <symbol> in <filename>/<namespace/<>
Causes any call to unqualified <symbolname> to be resolved in case of any name
clash,
by choosing the global with this name in <filename>/<namespace>. Changes are
global.
If any argument is not found or not valid, nothing happens.
Using "" as second argument removes any previous choice for the symbol. At any
time,
only zero or one symbol with a given name can be chosen.
2/
restrict <symbolname> in <filename>/<namespace> [to <filename>/<namespace>/""]
Restricts visibility of <symbolname> defined in first <namespace> to the
second <namespace> and any file included in it. If any argument is invalid,
nothing will happen. Using "" as second namespace lifts all restrictions.
Omitting the "to" clause restricts to current file.
In order to implement the latter, I added a new field in the SymTab entries.
I raised the values for SIZEOF_VAR_ENTRY and SIZEOF_ROUTINE_ENTRY accordingly
Now the question is: what about the value which is added to these constant
when TRANSLATE is nonzero? I couldn't figure out where it is used, and hence
whetherand how it would be affected by the change just described.
Is any change to the 24 or 33 part necessary?
TIA
CChriis
2. Re: Modifying entry sizes in eu.ex
- Posted by Robert Craig <rds at RapidEuphoria.com>
Nov 23, 2005
-
Last edited Nov 24, 2005
CChris wrote:
> In order to implement the latter, I added a new field in the SymTab entries.
> I raised the values for SIZEOF_VAR_ENTRY and SIZEOF_ROUTINE_ENTRY accordingly
>
> Now the question is: what about the value which is added to these constant
>
> when TRANSLATE is nonzero? I couldn't figure out where it is used, and hence
>
> whetherand how it would be affected by the change just described.
> Is any change to the 24 or 33 part necessary?
Don't worry about the TRANSLATE nonzero case.
There really shouldn't be any translator-related code in eu.ex,
but it was easier to leave a few bits of it in, here and there,
than to carefully strip it all out. My copy of eu.ex etc. contains
several large chunks of front-end translator code that are not included
in the PD source, since the translator is not PD.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
