Re: [opensuse] Quick perl question - why are @array[$num] and $array[$num] the same?
Sam Clemens wrote:
David C. Rankin wrote:
Randall R Schulz wrote:
On Thursday 01 May 2008 00:36, Sam Clemens wrote:
...
I gave up on perl. It makes my brain hurt -- like trying to read 1970's era BASIC code.
I concur. Perl verges on being an abomination. "Pathetically eclectic rubbish lister" indeed!
I once (in the Perl 4 era) wrote a code generation tool in Perl, but I no longer can even read that stuff.
If you're going to start programming things that go beyond what works well in BASH, you'd be better off with Python or Ruby or even Groovy.
Randall Schulz
That's real, real bad news Randall, I'm already 60% through perl.
It's worth taking a look at, if only for familiarization. But don't try to do a "monster" program with it. 10000 lines of shell-script is more maintainable than 100 lines of perl.
Well, My purpose for looking at perl was I wanted a more robust bash. I wanted something that had better file handling, data structures, loop and conditional expression support, regexp support, floating point, etc.. Just something that would allow me to do in 20-30 lines of code all (or at least 99%) the administrative stuff I need to do, but where I have run into limitations in bash. If I was ever going to do a big project, it would be in c/c++, (heaven forbid Fortran) something I already know. I thought perl would be a step up in scripting language from bash. Is that the wrong move? Would something else give me all perl's functionality in a better script language? I was really looking forward to the CPAN resource. You guys let me know what you think. Thanks. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 01 May 2008 08:57, David C. Rankin wrote:
Sam Clemens wrote:
...
It's worth taking a look at, if only for familiarization. But don't try to do a "monster" program with it. 10000 lines of shell-script is more maintainable than 100 lines of perl.
Well,
My purpose for looking at perl was I wanted a more robust bash. I wanted something that had better file handling, data structures, loop and conditional expression support, regexp support, floating point, etc.. Just something that would allow me to do in 20-30 lines of code all (or at least 99%) the administrative stuff I need to do, but where I have run into limitations in bash.
If I was ever going to do a big project, it would be in c/c++, (heaven forbid Fortran) something I already know. I thought perl would be a step up in scripting language from bash. Is that the wrong move? Would something else give me all perl's functionality in a better script language? I was really looking forward to the CPAN resource.
You guys let me know what you think. Thanks.
If you're already engaged with Perl, just stick with it. If you're a programming professional or want to be, you'll need to work with lots of languages and understand them and their strengths and limitations at a deeper level than someone who just wants to get some day-to-day, one-off tasks done and won't need to, e.g., support other people using or maintaining your code. Either way, having some experience with Perl won't be a bad thing.
-- David C. Rankin
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz wrote:
If you're already engaged with Perl, just stick with it. If you're a programming professional or want to be, you'll need to work with lots of languages and understand them and their strengths and limitations at a deeper level than someone who just wants to get some day-to-day, one-off tasks done and won't need to, e.g., support other people using or maintaining your code. Either way, having some experience with Perl won't be a bad thing.
No, I'm not looking for a career change. (though sometimes I wonder) Other than being a past aero-engineer, my current involvement with computers is simply keeping my office running and helping others out. I have 4 servers I baby sit and about a dozen or so other boxes. I do run across a number of uses for this knowledge in my practice though. We continually get document productions sent to us in electronic format in all different types, engineering specs, accounting data, email logs, digital images and video. We are required to digitally file all documents in the Federal court system. It is useful for me to be able to do whatever needs to be done to reformat/extract/merge the needed information and to be able to catalog in a database information related to each document. Linux is fantastic in this area and shell scripting really helps automate a large number of the required tasks. In doing that, I continually try to add new tools to my toolbox. perl is the next shiny new tool for my box. Thanks for your insight into the strengths and limitations and alternative to perl. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2008-05-01 at 10:57 -0500, David C. Rankin wrote:
Randall Schulz
That's real, real bad news Randall, I'm already 60% through perl.
It's worth taking a look at, if only for familiarization. But don't try to do a "monster" program with it. 10000 lines of shell-script is more maintainable than 100 lines of perl.
Well,
My purpose for looking at perl was I wanted a more robust bash. I wanted something that had better file handling, data structures, loop and conditional expression support, regexp support, floating point, etc.. Just something that would allow me to do in 20-30 lines of code all (or at least 99%) the administrative stuff I need to do, but where I have run into limitations in bash.
If I was ever going to do a big project, it would be in c/c++, (heaven forbid Fortran) something I already know. I thought perl would be a step up in scripting language from bash. Is that the wrong move? Would something else give me all perl's functionality in a better script language? I was really looking forward to the CPAN resource.
You guys let me know what you think. Thanks.
(quite) Some years ago i had to solve a nice puzzle. Eventually i cracked it, with pieces written in bash, csh, awk and sed. Then i was introduced into perl, and love it ever since, as it has all the goods of both (4) worlds. Only drawback is that you have to practice it daily... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Sam Clemens wrote:
David C. Rankin wrote:
Randall R Schulz wrote:
On Thursday 01 May 2008 00:36, Sam Clemens wrote:
...
I gave up on perl. It makes my brain hurt -- like trying to read 1970's era BASIC code.
I concur. Perl verges on being an abomination. "Pathetically eclectic rubbish lister" indeed!
I once (in the Perl 4 era) wrote a code generation tool in Perl, but I no longer can even read that stuff.
If you're going to start programming things that go beyond what works well in BASH, you'd be better off with Python or Ruby or even Groovy.
Randall Schulz
That's real, real bad news Randall, I'm already 60% through perl.
It's worth taking a look at, if only for familiarization. But don't try to do a "monster" program with it. 10000 lines of shell-script is more maintainable than 100 lines of perl.
Well,
My purpose for looking at perl was I wanted a more robust bash. I wanted something that had better file handling, data structures, loop and conditional expression support, regexp support, floating point, etc.. Just something that would allow me to do in 20-30 lines of code all (or at least 99%) the administrative stuff I need to do, but where I have run into limitations in bash.
For *THAT*, it's an excellant choice. In contrast, I once worked at a place where the backup scripts were several thousand lines long, written in ksh.
If I was ever going to do a big project, it would be in c/c++, (heaven forbid Fortran) something I already know. I thought perl would be a step up in scripting language from bash. Is that the wrong move?
depends on the size.
Would something else give me all perl's functionality in a better script language? I was really looking forward to the CPAN resource.
You guys let me know what you think. Thanks.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David C. Rankin wrote:
Sam Clemens wrote:
David C. Rankin wrote:
Randall R Schulz wrote:
On Thursday 01 May 2008 00:36, Sam Clemens wrote:
...
<snip>
Well,
My purpose for looking at perl was I wanted a more robust bash. I wanted something that had better file handling, data structures, loop and conditional expression support, regexp support, floating point, etc.. Just something that would allow me to do in 20-30 lines of code all (or at least 99%) the administrative stuff I need to do, but where I have run into limitations in bash.
If I was ever going to do a big project, it would be in c/c++, (heaven forbid Fortran) something I already know. I thought perl would be a step up in scripting language from bash. Is that the wrong move? Would something else give me all perl's functionality in a better script language? I was really looking forward to the CPAN resource.
You guys let me know what you think. Thanks.
I had to get to grips with Perl when I was required to do some customising of a fairly large web based application. Once I got over the initial WTF, began to appreciate its flexibility. Perl has extensive Modular capabilities and mutable syntax. Perl is strongest at anything that requires any form of textual manipulation, but you can probably do damn near anything with the language. (Perl::Inline gives the ability to link Perl to C/C++/Java libraries to do legwork so one can combine scripting and compiled code level functionality). The CPAN library is quite extensive. It is not an elegant language or easy language to learn, which in part is why the two major texts on the language are called the Llama and the Camel. However, like the two beasts in question it is good at getting the job done. It is a very powerful tool. - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFIGtw2asN0sSnLmgIRAhsXAKDq71oX3Pcbc0CKnVNnzYO6g4aKdgCfajtr YugqgNQwdm8yCNUiVgwJ3Ns= =7YIH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
David C. Rankin -
G T Smith -
Hans Witvliet -
Randall R Schulz -
Sam Clemens