OpenEuphoria

Re: include path problem [WAS: STANDARD EUPHORIA LIBRARYS]

• Posted by c.k.lester <euphoric at c?lester.c?m> Aug 06, 2007
• 553 views

CChris wrote:
> c.k.lester wrote:
> > I wanted this change primarily because CGI is so different from standard
> > program interfaces. I've been able to create a significant plugin system
> > for BBCMF that was not possible with the old include method.  Even now I
> > wish open() worked the same way; it would make for pure modularity.
> What about an open_path(filename,mode) which would use exactly the same
> mechanism that }}}
<eucode>include</eucode>
{{{

> uses?</font>

Yes, please. :)

Here were Rob's comments to me about modifying open():

"I really don't think you should mess with open().
It should remain a basic, efficient, primitive mechanism
for opening a file according to the rules of
the host operating system.

You should instead make your own search_open(), or
some such thing, that will take a list of directories,
from an environment variable, or whatever,
and search them according to whatever rules you like.
Don't force the rest of us to have to worry about your path
rules, and accidentally open a file that shouldn't be opened.

Lots of languages have a search path for opening include files.
I don't know of any that have a search path for their
basic, general, "open a file" operation."

So, I guess he said what you're saying, but I was too dense to get it. :/