In article <[EMAIL PROTECTED]>, "Alfred M. Szmidt" <[EMAIL PROTECTED]> wrote:
> > As long as the program simply does fork/exec, this is true. But > > the OP explicitly states that he is `importing' the script into > > the program. > > That's another word that isn't normally used to describe use of > scripts, so it's not clear what he meant. I assumed he meant that > he's simply invoking the script as a command. > > Which one? Importing or fork/exec? Importing However, I've seen the OP's followup, where he shows using the "import" command in Python. I'm not very familiar with that language, so I didn't know it used this word to refer to loading definitions from a library script. When he originally wrote "scripts", I was archaically thinking just of shell scripts. Programming in Perl, Python, and Ruby is much more like C programming, and the things you do by linking with libraries in C are done with "use", "require", and "import" in these languages. These are comparable to dynamic linking in compiled languages, so it would make sense to treat them equivalently for purposes of license application. -- Barry Margolin, [EMAIL PROTECTED] Arlington, MA *** PLEASE post questions in newsgroups, not directly to me *** *** PLEASE don't copy me on replies, I'll read them in the group *** _______________________________________________ gnu-misc-discuss mailing list gnu-misc-discuss@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-misc-discuss