RE: Training Using Windows

[email protected] (Chris Prince-Colbath)
Newsgroups perl.trainers
Message-ID <C29B240BA37BD4118FA500B0D049AA966456BE@HONTS328.homeoffice.wal-mart.com>
I install gvim or Winvi32 so I can at least have a semblance of UNIX.  Also
allows search and replace functionality, which Notepad and Wordpad severely
lack.

The main reason I use Winvi32 is that it will switch between ANSI and ASCII
so you can save the files appropriately for the platform you choose.  If you
ftp from UNIX to Windows in binary format, though, you don't have the
problem.

I use gvim for the syntax highlighting.  Great to help beginners see when
they forgot a quote or misspelled a keyword.

Both are freeware, I believe.

I have everyone keep a command window open and install doskey to make
re-execution easier.

Hope this helps.

Regards,

Christopher D. Prince-Colbath
Open Systems Database Administration
501-277-3575

***  Wal-Mart Confidential  ***

	-----Original Message-----
	From:	Peter Scott [SMTP:[email protected]]
	Sent:	Tuesday, April 10, 2001 8:41 AM
	To:	Simon Myers; [email protected]
	Subject:	Re: Training Using Windows

	At 01:16 PM 4/10/2001 +0100, Simon Myers wrote:
	>Hello.  I've been booked to do some Perl training for a company
that
	>uses Windows.  My Perl experience is nearly all from using it on
various
	>flavours of Unix.
	>
	>This shouldn't be a problem -- the course is on generic Perl
language
	>stuff.  It doesn't include anything like the Win32:: modules, so
the
	>content of it won't be a problem.
	>
	>I'm just slightly concerned over the execution, particularly of the
	>class exercises as the end of each section.  Can anybody who's done
this
	>kind of thing before offer advice on any pitfalls I ought to be
aware
	>of?

	  Wordpad is better than Notepad if any of your files come from
Unix; the 
	former handles the line terminators, the latter displays them as 
	boxes.  There are of course much better unbundled editors; gvim
works nicely.

	  Double clicking on a program will cause the output to flash in a
DOS 
	window and promptly go away.  I use something like

	END { print "Done, hit <RETURN>: " and <STDIN> if $^O =~ /Win32/ }

	  You will spend most of your excess time going, "Ok, just grep the
files 
	for the line containing -- oh, wait a minute --"


**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to 
whom they are addressed.  If you have received this email 
in error destroy it immediately.
**********************************************************************
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.