[Date Prev][Date Next][Thread Prev][Thread Next] [Search] [Date Index] [Thread Index]

Re: [MacPerl] We're all Macperlers on this bus...



At 14:40 -0500 98/06/15, Chris Nandor wrote:
> >} *Alternatively, maybe it's time to reconsider broadening the
> >} Mac-specific-only ground rules.  A little :-)
> >
> >I wouldn't mind that, either.
>
> The problem is twofold, I think:
>
> 1.  People apparently leave the list when we discuss non-MacPerl stuff.

I'd be very interested in what the majority of members consider
"non-MacPerl stuff".  I'd also be interested in the statistics regarding
people leaving, subject matter, etc.  I'm a very data-oriented sort of
person :-)

If I'm writing a script, using MacPerl, using BBEdit, using my Mac, using
Brad's nifty BBEdit extensions, that's MacPerl?  But when I send the script
over to a Unix box to run, or access a server on a Unix machine, then it's
not MacPerl? Is MacPerl-specific only the functions in the MacPerl:: and
Mac:: modules?  But not the other ones?  Unless they differ on a Mac of
course... (my brain hurts).

If I can't make an AppleScript thingie work, or my toolbox call is giving
weird output, I can ask the list.

But when I can't figure out whether I should be calling sysopen or open, I
get shuttled to a different forum, a forum that is probably going to tell
me that I should have known that this question was answered last September
in FAQ#57 paragraph b, subsection 14, the 3rd edition). And I probably
shouldn't mention that I'm using a Mac...

The problem with RTFM for Perl is that TFM is very large and distributed
and occasionally difficult to understand.  Once you understand what it
says, you realize that everything you needed to know was there all the time
(except, of course, when it needs an update in the next printing ;-).


> 2.  When we allow MacPerl stuff, we run the risk of increasing what I
                  ^^non??

> think is a comfortable traffic level (which also, in turn, causes people
> to leave the list).
>
> I am not necessarily opposed to it, however.


I'm not suggesting we open the list to any and all comers, any and all
questions.  As I said, my preference would be for posts in the context of
"I use a Mac && I use Perl".  Or even "I use MacPerl".

I'm not advocating Unix-specific questions, but to me, if it runs on a Mac,
under MacPerl (or was written on a Mac using MacPerl) it should be fair
game.

Paul Schinder said:
> If you're serious about this, what you should do is try to get the
> Perl Institute to sponsor the list.  They have a variety of lists
> <http://www.perl.org/maillist.html>, but no general purpose list.

I have no particular interest in starting a general purpose list. And my
preference would be not to start a new list at all, but to enhance the one
we have.

I want a MacPerl list on which a MacPerl user who is writing a script in
MacPerl does not have to worry about the fine distinction of whether his or
her question could just as readily have been asked of a script
written/running under Unix Perl and if so, wonder whether or not to ask it.
My preference would be for the determining factor to be _I use MacPerl_
rather than _and my question cannot possibly apply anywhere but on a
Macintosh_.

My guess is that by restructuring the criteria for postings to
(Mac)Perl-related rather than Mac(Perl)-specific we could win a lot without
losing too much.  We spend as much time telling people their questions
aren't germaine as we might answering them!

> > (While you're at it, someone should get them to list the MacPerl
> > list.)

Why didn't you send a note? :-)

OK, then... I just sent a note.

- V.
---
Vicki Brown, vlb@cfcl.com        |\      _,,,---,,_
Journeyman Sourceror      ZZZzz /,`.-'`'    -.  ;-;;,_
Scripts & Philtres             |,4-  ) )-,_. ,\ (  `'-'
http://www.cfcl.com/~vlb      '---''(_/--'  `-'\_)
P.O. Box 1269 San Bruno, CA  94066

***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch