in reply to Re: Not-So-FAQ about learning Perl in thread Not-So-FAQ about learning Perl
Please do keep us posted!
One half-baked notion I've had for younger, beginning programmers is that lessons could be written as POD or XML, then presented via a pager script. At appropriate points in the reading, the lesson would stop, and accept user input. The input would then be eval'ed for full effect. If there are errors, the pager script can assist in parsing the problem.
This way, learning the ins and outs of emacs (or vi or notepad or Komodo) can be saved until after the larger introduction to programming and Perl is done. Also, scripts can be partially prepared. The student doesn't need to spend time typing #!/usr/bin/perl (or even figuring out what the correct shebang is on their machine), it can be prefilled (so for the bits that are not integral to the lesson, this means that stray typos in those other areas will not interfere with learning progress). For students my daughter's age (8) I think not having to go through a lot of steps would keep them more focused during the learning process.
This type of interactivity was one of the things that made getting into BASIC on the old Apples and C-64s so easy. You typed your next line on the command line and it got put into your program in the appropriate spot. It was easy to LIST [start_line#-[end_line#]] your program.
Re: Re: Re: Not-So-FAQ about learning Perl
by puck (Scribe) on Dec 28, 2000 at 02:44 UTC
|
The fill in the blanks part is good. That is how some of
the
early assignments I did at Uni worked.
If the problem is "Write a program to print the integers
from 0 to 9, modify this program":
#include <stdio.h>
main {
int i;
for (i = 0; i < 10; i++) {
/* You're code here */
}
}
Okay, that's a really simple one, but you get the idea...
I assume that the Comp Sci department at my old Uni
(VUW) is the only
one that does that...
Cheers! | [reply] [d/l] |
|