Archive of UserLand's first discussion group, started October 5, 1998.
Re: Scripting on Linux (And general Unix)
Author: William Crim Posted: 5/17/1999; 8:43:39 PM Topic: Scripting on Linux Msg #: 6383 (In response to 6341) Prev/Next: 6382 / 6384
The general trend in Mac and Windows scripting seems to follow the philosophy, Make a program that does lots of things, and make interfaces for scripts. This makes sense, since Mac and Windows apps have OS and libraries that do most of the work for them.
In Unix, it is more of a bits and pieces approach. There are hundreds of programs, and the scripting is the glue that puts them together.
Now X-Windows takes a more Mac-Windows approach to scripting. X-Windows and various widget sets often have extensable and exposed frameworks that can be scripted. Usually the X-Windows widget sets are equally functionable with scripting as with C.
Often times if you want to send a message, or get info from a currently running program, you start another copy of the program from within the script. This isn't as wasteful as it sounds, because Linux won't load the same code into memory twice.(Wish Mac and Windows did that. ;-) ) This usually allows you to start communicating.
There are zillions of ways to do things in Unix, and scripting Unix is no exception. :-) Heck, there is even a program that will let you take a C Header file(*.h) and turn it into a Perl interface module.(Thereby giving Perl easy access to all those C functions.) Can't beat that. ;-)
There are responses to this message:
- Re: Scripting on Linux (And general Unix), Emmanuel M. Décarie, 5/17/1999; 9:22:35 PM
This page was archived on 6/13/2001; 4:50:15 PM.
© Copyright 1998-2001 UserLand Software, Inc.