Re: [binarycloud-dev] Another kneejerk suggestion for import()

[Justin F. <je...@ey...>]

Andreas:

Hey, I can live with that.  It makes the distinction
that I was wanting, would have sufficient information
in it for import() to allow me to have "dots" in
my file names, I think.

And, of course, you are correct about the economy
of a single call to "load a package" without
have to worry about that package's inventory/names
changing from underneath you.  Yes, I like that.

Right now, I am a bit confused, because I don't know
what the intentions of Alex are, and if this would
fit in the grand schems.  It seems to me, however,
that your idea is good, and aligns itself with what
Alex is thinking.  I also like your syntax better
than what I suggested as a kneejerk, that is, your
syntax only requires one argument to import().
That is better.

It still won't allow me, I think, to name my
layout files *.layout, my masters *.master, and
so forth.  Somehow, I still would like to retain
that possibility.  I also still feel that within
the system, for the only example that Alex/Odysseas
gave where *.php is "necessary", like using
the filter xml2php, there could be a solution.
That solution would be to put a "wrapping environment"
around those operations by, say, appending ".php"
before the operation, and stripping ".php" after
the operation.

Sure, this adds some overhead, but it is trivial.
Right now, you cannot even have your files named
*.PHP, or *.phtml, which is functionally identical
to *.php, but gives my "need" a bit more force.
Lordy, I hate the idea that, right now, I cannot
name my files

	*.layout

or as a partial compromise

	*.layout.php

because it throws away the ability of easily
constructing find(1) scripts or globbed
arguments to any argument to any of the
standard UNIX/Linux utilities needed for
easy administration.  If I had to do things
like name my files:

	file01Layout.php
	file07Master.php
	file09Module.php

and the go sed(1) everywhere in my scripts,
I would get very tired and irascable.  Er,
I am already tired and irascable... 

Again, I like your suggestion.

_jef

------------------------------------

Andreas Aderhold wrote:
> 
> Hi Justin,
> 
> > What about this syntax to ship enough information to
> > import() in order to distinguish "package" from "file":
> > import('a_file_name')
> > for importing a "true file object", and
> > import('package_name:object')
> > for importing an "object" from a "package"????
> 
> Another one could be:
> 
> Leave import for packages as is:
> import('binarycloud.core');
> import('binarycloud.core.Init);
> etc.
> 
> add resource handler for true files:
> 
> import('file:a_file_name');
> 
> .andi
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev

-- 
Justin Farnsworth
Eye Integrated Communications
321 South Evans - Suite 203
Greenville, NC 27858 | Tel: (252) 353-0722