Re: Simon Cozens' book
[email protected] (Salve J Nilsen)
| Newsgroups | perl.trainers |
|---|---|
| Message-ID | <[email protected]> |
Suddenly, Darren/Torin/Who Ever... uttered:
>
> When I wrote my Perl Course, I tried to break up the different datatypes
> with code structure so that people could write programs immediately even
> if they were rather trivial.
>
> So, the order my course materials and the course itself was in:
> 1. Scalars
> 2. Comparison and Truth
> 3. Arrays
> 4. Loops
> 5. Hashes
> 6. Subroutines
> 7. Introduction to File I/O
> 8. Regexes
> 9. References
> 10. Packages and Objects
> 11. Standard Libraries
> 12. CGI (why many of the people were there)
> 13. Cleanup (a session but not a chapter)
I'd suggest to add a sepererate step concerning _Context_. Lot's of
bugs (and headaches) can be avoided if the newbie perl programmer is
aware of how context is working... :)
The course I made (once upon a time at the University) focused a lot
more on "how not to fsck up" than "this is the syntax and these are
the semantics."
I'd appreciate it if someone could tell me if I was completely off
target. (I've only had a couple of the courses, but they were at least
reasonably popular 8)
Just my $0.02! :)
- Salve
--
#!/usr/bin/perl
sub AUTOLOAD{$AUTOLOAD=~/.*::(\d+)/;seek(DATA,$1,0);print# Salve Joshua Nilsen
getc DATA}$"="'};&{'";@_=unpack("C*",unpack("u*",':4@,$'.# <[email protected]>
'2!--"5-(50P%$PL,!0X354UC-PP%/0\`'."\n"));eval "&{'@_'}"; __END__ is near! :)