My vote is for McPL/TEXT. I can't recall the last time I opened a module to
read it's documentation by double-clicking it. I find it more convenient and
navigable to open from the dialog. I often want/need to look at the module
code, however, where it is more convenient to open from the finder.

Keary Suska
Esoteritech, Inc.
"Leveraging Open Source for a better Internet"

> From: Chris Nandor <[EMAIL PROTECTED]>
> Date: Mon, 15 Oct 2001 14:57:12 -0400
> To: "Scott R. Godin" <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: [MacPerl] Re: 5.6.1b1 problem .pm files
> 
> At 03:01 -0400 2001.10.15, Scott R. Godin wrote:
>> A>that's the way it should be.
>> 
>> Shuck is the pod file reader.
> 
> It is how I designed it, yes.  I am not strongly tied to the idea, but I
> figure 90 percent of the time, people will open a module file to read its
> documentation.  It doesn't affect the usage of the file at all.
> 
> If people have feelings about it one way or another, I'm all ears.
> 
> -- 
> Chris Nandor                      [EMAIL PROTECTED]    http://pudge.net/
> Open Source Development Network    [EMAIL PROTECTED]     http://osdn.com/
> 

Reply via email to