Re: Revised Namespace Proposal

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

On 6 Jul 2001, at 10:28, Travis Beaty wrote:


> 
> Howdy!
> 
> 
> On 5 Jul 2001, at 16:55, Robert Craig wrote:
> 
> > I read through the suggestions that people put forward
> > last week regarding the namespace issue, and 
> > I've come up with a fairly minimal solution 
> > based on what various people seemed to agree on.
> 
> <kersnip>
> 
> >     I'll also allow quotes around included file names, 
> >     in case someone wants to include a name with blanks in it, e.g.
> > 
> >           include "Program Files\\myfile.e"
> > 
> >     Otherwise the quotes aren't needed,
> >     and blank (whitespace) terminates the file name.
> 
> This is a wonderful idea, Mr. Craig, however I must agree with Derek that 
> quotations may not be the best delimiters, cause some goofy programmer, like 
> me, might try this ...
> 
> CONSTANT theFile = "program files/thisun.e"
> 
> include theFile

HEY!!! I *like* that one, Travis, great idea!!! Then when we can re-include
files, we are a
step closer to executing variables! smile  Speaking of such,, and turbo pascal,,
let me
toss in the idea of unlinked dynamic overlays for Eu. They could be altered
while
unlinked, and reincluded while running to exec new code?

Btw, one reason i like DDE is that a program that has a DDE name can be shut
down,
recoded, and fired back up with no complaints by the OS when another programs
tries
to send it something while not running. I don't know if windoze drops the bits
into $null
or what, but i routinely kill off DDE instances to free up resources on the
puter in a
crunch, and restart them with no errors. Naturally, the DDE programs handshake
and
know when the other hasn't replied, and deal with it. Executing vars is one way
a
singlethreaded Eu could accomplish the same thing, simply by reloading Travis's 
theFile above.
 
> I also like Derek's C-like approach, using <> as delimiters.

Except that the filename is a sequence, and using <> would break the rule that 
sequences are bounded by ". How about {} instead of <>? Since they are a
sequence,
i'd go so far as to make it mandatory that the filename be in "". I use them as
default,
so i don't have to exec the rule "if equal(SpaceInFilename,TRUE) then use quotes
end
if" in my limited wetware.

Kat

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

Search



Quick Links

User menu

Not signed in.

Misc Menu