Anonymous user
Talk:Executable library: Difference between revisions
→Too complicated: Not quite.
m (Try to fix the last commit by Mcandre. The page had 2 copies of almost everything.) |
(→Too complicated: Not quite.) |
||
Line 51:
==Too complicated==
This whole thing is getting too complicated. The purpose of ScriptedMain is to list code in as many languages as possible that does this: [http://docs.python.org/library/__main__.html http://docs.python.org/library/__main__.html] For lack of a better name, it can be called "scripted main". It reinforces the idea that such a function runs when the script is run on its own, not when the module is imported by other code. --[[User:Mcandre]]
:Not quite. The point is more like you can have a useful library for other programs to access ''as well as'' a useful program in its own right ''from the same file''.
:Your suggested name isn't descriptive. It is hard to put a name on something using just two words, but I think "Executable library" has the advantage of being more descriptive.
:This tasks was written to allow languages to give a concrete example of an executable library where they can focus on the executable library part of the task but using part of a more simpler task as the basis of the library, that already has many examples - the extra work would be mostly on turning it into an executable library that could be demonstrated to work, and comparable in how the language gets things to work, in both aspects of the task: as a library and as an executable.
:Too complicated? I don't think the task is overly complex for what it attempts to describe, as the task might well be foreign to the RC audience and so programmers need guidance in trying to nail things down, remember, executable libraries might be ''popular'', (such as being mentioned in official documentation), in maybe only Python. It's certainly not a popular technique in C :-)
: --[[User:Paddy3118|Paddy3118]] 02:24, 6 August 2011 (UTC)
| |||