On Tue, May 17, 2005 1:09 am, Martin B�hr said: > On Mon, May 16, 2005 at 03:20:24PM +1200, John Carter wrote: >> With scripting languages real life problems are typically about >> "glueing" >> together other existing apps. > > yes and no. > for that to hold true, maybe we need to split the definitions of > scripting languages: > > glue: shell, perl, ruby > non-glue: php, python, pike > > i am not actually sure about php here. it is used to glue things > together, but not in the same way as the above glue languages. > same with python. > > pike otoh is most certainly not a glue but an application language. > you could call pike a network glue language. socket handling is one of > pikes strenght. (a webserver in less than a dozend lines of code? :-) > > the difference here is mostly that reading stdout from another > application is trivial in glue languages, and reading a socket is > harder, while in pike it is the other way around because reading from > other apps is not done as often. > > greetings, martin. > -- > cooperative communication with sTeam - caudium, pike, roxen and > unix > offering: programming, training and administration - anywhere in the > world > -- > pike programmer travelling and working in europe > open-steam.org > unix system- bahai.or.at > iaeste.(tuwien.ac|or).at > administrator (caudium|gotpike).org > is.schon.org > Martin B�hr http://www.iaeste.or.at/~mbaehr/ >
I'm sorry, but it's the *operating system* that provides the ability to glue programs together. *nix os's work fine, but try using the tools you describe on one of Wesleys toys and see how much glue you find. To the best of my knowledge, *all* languages that run on *nix have the ability to read stdin/write to stdout, so by your definition, all languages are glue. But without the | functionality provided by the os, that's meaningless. Steve. -- Windows: Where do you want to go today? MacOS: Where do you want to be tomorrow? Linux: Are you coming or what?
