Globals and shrouding

new topic     » topic index » view thread      » older message » newer message

G'day all

A couple of thoughts on shrouding and globals:

1. Rob, could the shroud function be changed (with some sort of user
selection) to leave globals in clear code? Anything starting with
"global" could be left unshrouded - this would apply to both data
and function/procedure definitions. The code, and the use of the
global variables inside the code, would still be shrouded as they
are now. 

This would give the curious (including other Eu developers) a way to
determine what global data is included in a shrouded library, as
well as what parameters are required for global routines.

This "unshrouding" could also be used with "include" lines, so that
users of the library could figure out what other libraries need to 
be available to make this library work correctly.

2.  Could libraries be developed in pairs, with one half containing
the global stuff and the other half the "non-global" (ie everything
else) stuff? That way, the non-global guts of the library could be
shrouded, but the global part be left in clear text. Any includes 
could go with the global part.


Number 1 is work for Rob, number 2 is (lots of) work for everyone
else...

Another $0.02 contribution

Regards
Tony

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu