OpenEuphoria

Re: Store Includes

• Posted by DB James <larch at adelphia.net> Jul 19, 2005
• 538 views

> 
> Hi Quark,
> 
> Actually, my question was a little more general, but what you are
> talking about is good to think about too.
> 
> All i really wanted to know was this:
> 
> Can you send your program a program file set that uses Euphoria's
> namespace feature and have it create a lumped program file
> with no namespace prefixes that runs the same as the original
> set of files?
> 
> I guess ideally you could also make an exw:
> 
> include this.e
> include that.e
> include thisothertoo.e
> 
> and send it to your program to create a single file library right?
> 
> When you say duplicate names, you mean two names like this:
> 
> Window:Create(...)
> MyThing:Create(...)
> 
> where the 'Create's occur in different files?
> 
> Or do you mean something else?
> 
> 
> Take care,
> Al
> 

Hi Al,

The first thing that now comes to my mind is "YOW!".  I now see the
implications of your question and the answer is "maybe".  I am primarily
a DOS programmer, and have those blinders on sometimes when I tackle
things, as was the case with Mash.ex.  I hve never used the namespace
convention, but for those who do use it, (perhaps especially in Windows
programming?), it may well be important or critical, for all I know.

I think I can see a way to do what you ask without tossing everything out
and beginning again (or tossing Mash.ex on the heap with other experiments
that didn't work out).

Thinking aloud, if a parse found a namespace item in an include line,
and later a colon'ed reference to a routine or type, then the referred
gizmo could be made into a unique name by prepending the name
of the namespace to it wherever it is found in the appropriate sections
of the code.  I so surmise, anyway.  That would do what you asked about,
but if the declare were in yet another file (if that ever happens), I think
I'd be sunk.  So, Question: are all namespace references to items declared
in the named include file?  If so, this is possibly a "go".

Meanwhile, I have used Juergen's file_ln.e to improve the file-handling 
of all three programs.

If nothing else comes of all this, I am learning a lot of interesting tricks
in coding and error-reporting.  I have a file in C:\Euphoria called
Debug.txt that I load into Edita, and reload it frequently, that shows
what is happening in critical areas of the code as I run tests, because of
writing to that file all the data I need to see.  I turn this reporting on
and off as I need to.  Very useful.

Thanks for your interest and comments.  It is helping a lot.

--Quark