Re: 5.1 package proposal and Kepler libs

--Apple-Mail-7--391377600
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=ISO-8859-1; format=flowed


El 08/12/2004, a las 1:19, Martin Spernau escribi=F3:

Hi again,

(Stripped down version of thread follows)

>> The "compat-5.1.lua" script must be loaded before [...] our=20
>> bootscript. A good place to load it is at the end, [...]
>>
>> [...] use LUA_PATH to find scripts and LUA_CPATH for binary modules.=20=

>> [...] Add the LuaCheia paths to that variables [...] from =20
>> "luacheia_wrapper.c" [...] before spawning the Lua interpreter.
>
> Okay
>
>> A.)  Link "compat-5.1.o" into "lauxlib.{so,a}", and merge the=20
>> function definition from "compat-5.1.h" into "lauxlib.h". [...]
>
> This seems to be the 'easiest' approach.
> Are we sure that in 'official' Lua 5.1 things will be there also? Is=20=

> that 'fixed'?

I have been reading sources from Lua 5.1-work3 and it seems that=20
Compat-5.1 follows its behaviour. The only difference is that the=20
luaL_module in "compat-5.1.c" is called luaL_openlib in=20
"src/lib/lauxlib.c" from the 5.1-work3 sources.

When migrating from lua-5.0.2 + compat-5.1 we'll have to rewrite all=20
calls to luaL_module to luaL_openlib ("sed" is a good friend!).

>> Regarding module adaptation [...] we can still load our modules=20
>> without modifying them. [...] When loading a module that uses the new=20=

>> module system via the "cheia.load" function we can print some kind of=20=

>> "deprecation warning" [...]. In the future we'll have to bury=20
>> "cheia.load" and friends [...]
>
> I do not have a big problem with dumping cheia.load and friends now or=20=

> later... The evolution of LuaCheia has seen more than one move like=20
> this ;)

The same goes for me. The new module system is far superior, as well as=20=

"standard", which is a Good Thing (tm).

> [...] The only modules I imagine that could be a 'problem' are=20
> gluahost based ones... or any module using a non-standard loading=20
> mechanism for that matter...

Regarding gluahost-based ones I feel like Asko might appear someday=20
with the "magic silver bullet" that will integrate them with the new=20
module system (it really would be soo nice).

The problem with modules using nonstandadrd loading methods is worse.=20
What we can do is saying in the docs that using other loading methods=20
than the Lua-standard one is discouraged and unsupported by us. But=20
everyone can do things assumming risks, of course!

> Okay, that's just my 2 cents.

Not only 2c! You raised some interesting questions ;-D

> Do I understand this right: we can expand LuaCheia in a way that we=20
> can used 'both worlds' side by side? That would be my favorite.

Just that. Only some changes needed to "cheia.load" (and perhaps minor=20=

changes in other functions) in order to co-operate with the new=20
"require()". I strongly believe that we can have both "cheia.load" and=20=

the new "require" working side-by-side with a quite small effort.

(But I think that it would be better to abandon "cheia.load" when=20
possible, so LuaCheia could get a "Lua-standards-compliant" mention,=20
and avoiding annoyances with "cheia.load" vs. "require").


I would like to see more feedback on the list before implementing=20
nothing -- only to know wether there is a general feeling about this=20
(important, I think) issue.

Thank you all in advance,

-ap

--Apple-Mail-7--391377600
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: Mensaje firmado digitalmente
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAkG2WvUACgkQghBwwjayrGTx0QCgiSU7lk+6db9dYBvZz6L7IQll
Or8AoPzP7E4RM8I5tqrAE6jGte3oRRnJ
=GLqo
-----END PGP SIGNATURE-----

--Apple-Mail-7--391377600--



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/