[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: RE: Lua libraries
- From: Nick Trout <Nick.Trout@...>
- Date: Wed, 30 Jan 2002 10:59:13 -0000
> Don't some platforms require the executable to know the
> absolute path to
> the shared lib while not providing the app with info about
> the path the
> executable?(Linux?) So the shared libs are essentially
> required to be in
> system folders and therefore seriously complicate user-level
> applications - admin access is required to install the libs & whose
> shared lib gets installed if two apps have a shared lib with the same
> name? It's dangerous to make the assumption that everyone
> that will want
> to be able to run a lua app is also a sysadmin.
>
> Making shared libs the standard for lua-addons would make lua both
> platform dependent and sysadmin dependent.
How do Lua and Python cope with this? I dont think you need admin privileges
to install new modules on Python on any platform? (could someone please
inform me otherwise?)
So far as I know this would be very simple cross platform, you could just
have a directory/s which you dump your libs into, make sure its in LUA_PATH
and require the module.
Just because a standardised framework exists to do this doesnt mean that you
cant do it the current way. You should still be able to combine any
libraries with your app and build a single executable if you so require as
Lua may be embedded too. The flexibility of use of Lua still needs to be
there.
Nick