Talk:Executable library: Difference between revisions
→executable Shared Objects?
(→executable Shared Objects?: Probably, mainly, dynamic languages.) |
|||
Line 23:
:Most likely. It should be possible in several dynamic languages, and is heavily endorsed by Python.--[[User:Paddy3118|Paddy3118]] 18:48, 10 May 2011 (UTC)
::Alternatively: currently the task does not require the library be a single file -- it could easily be a directory or more properly a set of files within a directory. (And if it were changed to be required to be implemented as a single flat file it might be possible to do something by wrapping the necessary pieces in a manner something like a self extracting archive, which when used normally is an executable but can be told to extract the needed library elements at compile time, with an invocation that would need to go in the makefile or msbuild file or whatever. (Though, of course, the task could also be changed to prohibit the generation of object code at compile time, but I think most compilers generate intermediate object files as a normal part of the compilation process..)) --[[User:Rdm|Rdm]] 20:07, 10 May 2011 (UTC)
| |||