1. PERL - (Really just a stone in the side, isn't it?)
I am sure no one is offended by a person's desire to use PERL. I guess
this little stripped down version of PERL ( we call it Euphoria) doesn't do
what we want, we should find another place to play. (Please, do not let
this infer that I think Euphoria is not serious. I know it is to me.) If
you will go back to programming in PERL, you''ll have lot's of time to
decipher your code. (While you are waiting on the programs to run!!!)
I know, PERL does have so many other features. But the real test of a
program is not how covenient it was to type! Number one, does it perform
the function for which it was designed, at maximum utility? Number Two, is
it sufficiently re-usable so as to decrease additional production and
maintenance. Okay, I use mostly visual development products to achieve the
aforementioned results. But sometimes I have to do some extensive OS
coding. (And I like Euphoria for that.) If you want easy typing, develop a
preprocessor or use a preprocessor already developed.
Finally, I probably use Euphoria less than any of you. Frankly, that is the
reason I registered it. I needed the additional lines to be subject to
adequate error reporting. I love Euphoria, but it is not the best solution
for my entire environment. However, I use it when I need fast, small
programs. (Such as a print spooler that serves about 200 users. It checks a
directory queue every 3 seconds and sends the files to the appropriate
Novell Queue. I use this to print output created by an old NT client/server
product that cannot print to the Novell Queues directly. It has saved us a
ton of dollars and additional hardware.)
Joe Phillips, Assistant Director
Information Technology Services
Texas Wesleyan University 817-531-4284
2. PERL - (Really just a stone in the side, isn't it?)
I posted a question a while back about Euphoria versus these other
languages, such as Java, Perl, even Python and TCl.
A key advantage of these other languages is that it can work in more
environs than Euphoria.
The bottom line is, as it is for humans, see Euphoria for what is it, and=
don't see it for what it isn't. If its useful, work with it. One can us=
e
the public domain version without obligation. Then, when you get
frustrated writing large programs, register it. Don't find it useful? =
Then don't use it.
--Alan
=
