ClosestStorm / v8cgi

Automatically exported from code.google.com/p/v8cgi
BSD 3-Clause "New" or "Revised" License
0 stars 1 forks source link

What about multiple LibraryPaths? #28

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
While playing with the new beta I tried the mykesx' examples and would like
to propose the application of multiple libary paths like php.ini does it.
for example the core lib + the additional weblib and extra for a
framework-lib (maybe raccoon). 

also we need an API for the mykesx-modules ^^

angel

Original issue reported on code.google.com by bienmano...@googlemail.com on 21 Oct 2009 at 11:43

GoogleCodeExporter commented 9 years ago
Makes sense.

Also note that libraryPath might be in future changed to provide compatibility 
with
CommonJS Modules/1.1 proposal. This standard uses "require.path" variable to 
store
top-level search paths.

Original comment by ondrej.zara on 22 Oct 2009 at 10:53

GoogleCodeExporter commented 9 years ago
the path-variable is a good idea, it enables to configure autoloaders, like the
php-frameworks use. 

My other question concerns the additional webkid or weblib functions, that I 
program
last few days. I consider to open a project on github for that if someone want 
to
fork with. What do you think, is it practical and basical enough and makes 
sense for
integration into the v8cgi release as sub-folder of lib? 

Original comment by bienmano...@googlemail.com on 31 Oct 2009 at 12:04

GoogleCodeExporter commented 9 years ago
I believe that this should be discussed on the mailinglist, rather than as 
comments
to an unrelated issue :)

I have not seen your webkid library so far, so I cannot judge it. However, it 
might
be reasonable for you to create a branch and commit webkid there.

The only thing I do not want to happen is that we start offering multiple ways 
of
achieving the same goal. Therefore, all libraries which focus on the same thing
should have coordinated development to prevent code diffusing.

Original comment by ondrej.zara on 31 Oct 2009 at 9:56

GoogleCodeExporter commented 9 years ago
Implemented in revision 635. Also the path is now located in "require.paths" 
and not
Config.libraryPath.

Original comment by ondrej.zara on 2 Nov 2009 at 12:48