Once again we see this truth:
Those who can, do. Those who can't, teach...and come up with their own
definitions of things like this showing how little experience they really
have with real world situations. I'm sure their explanation makes themselves
feel superior, and at the same time shows the rest of us how little they
really know.
This professor needs to get his hands on Perl, get in the real world, and
see what it he can really do with it. After he has experience with that THEN
he might be qualified to give an opinion about Perl.
However, because the educational institutions are so full of these types,
many colleges still require Cobol to be taken if you are pursuing a CS
degree. I suppose they think they're offering something useful that'll help
you in today's world of computers - that by itself shows how out of touch
most of the professors with opinions such as those you gave know about the
real world.
Steve
-----Original Message-----
From: Jon Acierto [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 17, 2001 11:47 AM
To: [EMAIL PROTECTED]
Subject: PERL IS NOT A HIGH LEVEL LANGUAGE
Hello Guys It's me again,
After getting all the feedback from this maillist on my "High Level"
question AND going to an online dictionary and finding out that Perl Does
fit the definition of a high level language, I get this from the Admissions
Councellor at the U.W. ext.:
Jon, thank you for your inquiry.
I sent your description of your programming background to the C++
application reviewer and received this input:
"i have to agree with will's assessment. perl is not a high level
language. it amounts to a scripting language. simply having 2 years of
working with perl says nothing about whether he has worked on more complex
problems or has developed the programming skills necessary to understand
and solve such problems from ground up. in addition, does he have - in any
language - the understanding of more advanced data structures...with 2
years of serious cobol for example should bring familiarity with files,
records, and other such data types."
Jon, if you have the prerequisite background as described above, then you
will need to document and support it in your C++ application. Otherwise,
you will need to decide how you want to expand your programming experience.
In the UWEO program offerings, the C program would help you do this.
Can someone please help me explain to these people that writing Perl for 2
years says about as much of my ability to program and understand "advanced
data structures" and having worked on "more complex problems" as spending
those 2 years with C. Am I wrong? I know that if I describe to them the
OOP in Perl that I've done as well as all the work I've done with files and
records with data extraction (binary and ascii) that they would
understand. But is it just me or do these people not know anything about
Perl?
Jonathan Acierto
Perl Programmer
Ocentrix Inc.
206.691.7603
[EMAIL PROTECTED]
A famous linguist once said:
"There is no language wherein a double
positive can form a negative."
YEAH, RIGHT
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
