Re: Shrouding

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

From: Tony Bucholtz <tony_bucholtz at hotmail.com>
> G'day all
> 
> Robert Craig wrote:
> > If you choose the "scramble" option, then nobody can
> > read anything, but you can document the nice global
> > names you used in your original source file, and people 
> > who include your file can use them.
> 
> Maybe what we need is a combination of some of the earlier ideas, 
> such as:
> 
> 1. Preprocessor to prepend a comment block regarding globals and
> includes, extracted from the code
> 2. The "with shrouding" and "without shrouding" directives
> 3. Expand the "with/without shrouding" directives to also imply
> "with scrambling" and "without scrambling", to *always* leave the
> comment block (and anything else the author wants to reveal) in
> clear text

I believe that adding 'clear text' comments to the start of an otherwise 
shrouded file is an excellent one - distribute one file instead of two, 
and your docs can never get out of sync with your library. 

Probably there is a technical reason why Rob can't do this:
I think Euphoria looks at something (the first few bytes, perhaps) of 
each file when it is included, and ships it off to the 'deshrouder' 
routine if necessary. Probably, once a file is determined to be in plain 
text, i.e. a readable include file, it goes straight to the interpreter.

Maybe it would require a complete re-design of the interpreter to make 
it smart enough to handle mixed files.

Regards,
Irv

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

Search



Quick Links

User menu

Not signed in.

Misc Menu