[24639] in Perl-Users-Digest
Perl-Users Digest, Issue: 6803 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Aug 3 12:46:38 2004
Date: Tue, 3 Aug 2004 09:45:42 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 3 Aug 2004 Volume: 10 Number: 6803
Today's topics:
CGI parameter separation characters <musiphil@bawi.org>
Re: CGI parameter separation characters <noreply@gunnar.cc>
Re: CGI parameter separation characters <jurgenex@hotmail.com>
Re: CGI parameter separation characters <invalid-email@rochester.rr.com>
Re: CGI parameter separation characters <invalid-email@rochester.rr.com>
Re: CGI parameter separation characters <noreply@gunnar.cc>
Re: CGI parameter separation characters <spamtrap@dot-app.org>
Re: CGI parameter separation characters <flavell@ph.gla.ac.uk>
Re: CGI parameter separation characters <joe+usenet@sunstarsys.com>
Re: CGI parameter separation characters <musiphil@bawi.org>
Re: CGI parameter separation characters <flavell@ph.gla.ac.uk>
CGI::Echo V 1.04 <ron@savage.net.au>
CGI::Explorer V 2.04 <ron@savage.net.au>
CGI::Formalware V 1.12 <ron@savage.net.au>
CGI::Session::ExpireSessions V 1.03 <ron@savage.net.au>
CGI::Session::MembersArea V 2.01 <ron@savage.net.au>
CGI::TabPane V 1.04 <ron@savage.net.au>
Re: Class quandry <webmaster @ infusedlight.net>
Re: Class quandry <spamtrap@dot-app.org>
Re: Class quandry <Joe.Smith@inwap.com>
Re: Class quandry <spamtrap@dot-app.org>
Re: Class quandry <Joe.Smith@inwap.com>
Class::DBI::Schema2Code V 1.01 <ron@savage.net.au>
Class::Tree V 1.24 <ron@savage.net.au>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 24 Jul 2004 20:01:27 -0700
From: Seungbeom Kim <musiphil@bawi.org>
Subject: CGI parameter separation characters
Message-Id: <cdv7tm$qub$1@news.Stanford.EDU>
Bob Walton wrote:
> The broken crappy code you posted doesn't even
> recognize that ; is a valid parameter separation character, in addition
> to & , for example.
This might be out of topic, but I'm curious which document specifies
that ';' is a valid parameter separation character in addition to '&'.
I couldn't find it in the CGI/1.1, CGI/1.2 specifications.
--
Seungbeom Kim
------------------------------
Date: Sun, 25 Jul 2004 09:55:43 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: CGI parameter separation characters
Message-Id: <2mh7euFmtad8U1@uni-berlin.de>
Seungbeom Kim wrote:
> Bob Walton wrote:
>> The broken crappy code you posted doesn't even recognize that ;
>> is a valid parameter separation character, in addition to & , for
>> example.
>
> This might be out of topic, but I'm curious which document
> specifies that ';' is a valid parameter separation character in
> addition to '&'. I couldn't find it in the CGI/1.1, CGI/1.2
> specifications.
It's not. But ';' is often used in query-strings.
Now, an URL with a query-string results in a GET request, while the
original subject of this thread made clear that the OP asked about
POST requests. Accordingly, the code posted by the OP is not "broken"
because of only recognizing '&' as a param separator. It's not
"broken" for any other reason either, but it probably does what it's
supposed to do just fine.
However, in this group people often post comments like that, blunting
the intellect. They do it in order to let you know that you are a
moron if you don't use CGI.pm (or possibly some other module/library)
for parsing CGI data. To make their point, they typically claim that
code like the one the OP posted is "broken" since it doesn't handle
various things that it was never supposed to handle. Often they also
mention irrelevant security aspects. An example of the latter is that
Bob mentioned denial of service attacks, and then he posted code that
is just as exposed to such attacks as the code the OP had posted...
Consequently, beware of this group if you want to *learn* something
about CGI, other than 1) it's off topic here and 2) you should use CGI.pm.
Now, there are good, perfectly valid reasons for using CGI.pm, just as
there are good reasons for using other modules when feasible. It's a
shame IMO that people advocating the use of the module can't stick to
those reasons.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Sun, 25 Jul 2004 12:48:05 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: CGI parameter separation characters
Message-Id: <9_NMc.3900$Nu4.3649@nwrddc01.gnilink.net>
Gunnar Hjalmarsson wrote:
[...]
> Consequently, beware of this group if you want to *learn* something
> about CGI, other than 1) it's off topic here and 2) [...].
AMEN to that!
jue
------------------------------
Date: Sun, 25 Jul 2004 20:26:16 GMT
From: Bob Walton <invalid-email@rochester.rr.com>
Subject: Re: CGI parameter separation characters
Message-Id: <410416B1.40206@rochester.rr.com>
Seungbeom Kim wrote:
> Bob Walton wrote:
>
>> The broken crappy code you posted doesn't even
>> recognize that ; is a valid parameter separation character, in
>> addition to & , for example.
>
>
> This might be out of topic, but I'm curious which document specifies
> that ';' is a valid parameter separation character in addition to '&'. I
> couldn't find it in the CGI/1.1, CGI/1.2 specifications.
>
Well, I don't know what document it is specified in, but there is a
discussion about it in the docs for the CGI module:
perldoc CGI
in the "PRAGMAS" section, under the -newstyle_urls and -oldstyle_urls
pragmas, and stuff in the CGI.pm code itself. There are lots of web
references to the & pair separator being deprecated and replaced with ;
as the separator. Maybe someone in a CGI-oriented newsgroup would know
better where this appears in the standards?
--
Bob Walton
Email: http://bwalton.com/cgi-bin/emailbob.pl
------------------------------
Date: Sun, 25 Jul 2004 20:41:19 GMT
From: Bob Walton <invalid-email@rochester.rr.com>
Subject: Re: CGI parameter separation characters
Message-Id: <41041A37.9040002@rochester.rr.com>
Gunnar Hjalmarsson wrote:
> Seungbeom Kim wrote:
>
>> Bob Walton wrote:
>>
>>> The broken crappy code you posted doesn't even recognize that ;
>>> is a valid parameter separation character, in addition to & , for
>>> example.
>>
>>
>> This might be out of topic, but I'm curious which document
>> specifies that ';' is a valid parameter separation character in
>> addition to '&'. I couldn't find it in the CGI/1.1, CGI/1.2
>> specifications.
>
>
> It's not. But ';' is often used in query-strings.
Hmmmm...check out:
perldoc CGI
in the PRAGMAS section under the -newstyle_urls and -oldstyle_urls pragmas.
...
> Bob mentioned denial of service attacks, and then he posted code that
> is just as exposed to such attacks as the code the OP had posted...
True, but easily fixed with the addition of
$CGI::POST_MAX=100000;
or so at the beginning of the script, as one can note in
perldoc CGI
in the "Avoiding Denial of Service Attacks" section. My code was
intended to illustrate the ease of using the CGI module, but would have
been better with that addition.
> Consequently, beware of this group if you want to *learn* something
> about CGI, other than 1) it's off topic here and 2) you should use
> CGI.pm.
Agreed. Point well made.
...
--
Bob Walton
Email: http://bwalton.com/cgi-bin/emailbob.pl
------------------------------
Date: Mon, 26 Jul 2004 00:20:58 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: CGI parameter separation characters
Message-Id: <2miq5gFmi1vhU1@uni-berlin.de>
Bob Walton wrote:
> Gunnar Hjalmarsson wrote:
>> Bob mentioned denial of service attacks, and then he posted code
>> that is just as exposed to such attacks as the code the OP had
>> posted...
>
> True, but easily fixed with the addition of
>
> $CGI::POST_MAX=100000;
>
> or so at the beginning of the script,
Yes, or without CGI.pm by simply doing something like this:
unless ( $ENV{CONTENT_LENGTH} > 100000 ) {
# read STDIN and parse the data
} else {
# do something else
}
But you stripped the context in which I made that comment. You brought
up the risk for DoS attacks as a reason for using CGI.pm (which it
isn't), followed by code that included "use CGI" etc. but without any
limitation of POSTed data. By doing so, you sent the incorrect message
to the readers of this group that if they only use CGI.pm, they are
protected against DoS attacks. (Joe S. made a similar incorrect
comment in comp.lang.perl in reply to the same OP.)
That's nothing but desinformation, and since we are talking about a
significant *security* issue that people are made believe is
automatically taken care of by CGI.pm, it's the worst kind of
desinformation!
Bob, Joe, and (previously) several other regulars: Why do you
repeatedly do that? Why??
>> Consequently, beware of this group if you want to *learn*
>> something about CGI, other than 1) it's off topic here and 2) you
>> should use CGI.pm.
>
> Agreed. Point well made.
Do you really think so? I doubt it was, since I failed to include that
you should not only expect to not learn CGI, but in addition to that
you should be aware of *incorrect* statements about CGI being made
frequently, also by knowledgable regulars. :(
Many posters here seem not to want to discuss Perl programs that are
to be used in a CGI context. That's fine. But then they'd better keep
their mouths shut rather than posting desinformation.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Sun, 25 Jul 2004 18:42:44 -0400
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: CGI parameter separation characters
Message-Id: <juednclzgYr4qpncRVn-ig@adelphia.com>
Bob Walton wrote:
> as the separator. Maybe someone in a CGI-oriented newsgroup would know
> better where this appears in the standards?
I think that part of the problem is that there is no CGI "standard" as
such. The closest thing we have to one is NCSA's original documentation:
<http://hoohoo.ncsa.uiuc.edu/cgi/>
There appears to have been an attempt made to organize and submit an RFC
to the IETF, thus creating a formal standard, but that attempt appears
to have died on the vine:
<http://cgi-spec.golux.com/>
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Mon, 26 Jul 2004 00:26:43 +0100
From: "Alan J. Flavell" <flavell@ph.gla.ac.uk>
Subject: Re: CGI parameter separation characters
Message-Id: <Pine.LNX.4.53.0407260007460.5613@ppepc56.ph.gla.ac.uk>
I know this is the wrong place; but as the topic has come up, I think
this is worth saying, if you'll excuse me:
On Sun, 25 Jul 2004, Sherm Pendley wrote:
> I think that part of the problem is that there is no CGI "standard" as
> such. The closest thing we have to one is NCSA's original documentation:
>
> <http://hoohoo.ncsa.uiuc.edu/cgi/>
It's a respectable point of view, don't get me wrong, but those old
NCSA specs are a bit chatty and vague...
> There appears to have been an attempt made to organize and submit an RFC
> to the IETF, thus creating a formal standard, but that attempt appears
> to have died on the vine:
>
> <http://cgi-spec.golux.com/>
It has stopped proceeding to a more-formal stage, fair comment; but
the CGI/1.1 draft had as its goal:
Goal: Clearly and concisely codify "current practice" of CGI/1.1
usage on the Web as of 2000.
and I'd say it has achieved that goal well. I would definitely
recommend consulting it as a reliable source of "current practice",
irrespective of its position on the IETF's greasy pole. IMHO.
But the issue of using semi-colon as the alternative delimeter in
composed GET URLs is codified in the *HTML* specifications, starting
with RFC1866/HTML2.0. The CGI specification does not go into detail
about the format of the QUERY_STRING, but cites other relevant
specifications for it. With POST, on the other hand, the problem
simply doesn't arise for which the semi-colon is the suggested
solution, and so no solution is really needed.
I'd better shut up now.
------------------------------
Date: 26 Jul 2004 12:10:36 -0400
From: Joe Schaefer <joe+usenet@sunstarsys.com>
Subject: Re: CGI parameter separation characters
Message-Id: <87r7qyda0z.fsf@gemini.sunstarsys.com>
"Alan J. Flavell" <flavell@ph.gla.ac.uk> writes:
[...]
> With POST, on the other hand, the problem
> simply doesn't arise for which the semi-colon is the suggested
> solution, and so no solution is really needed.
FYI: the semicolon is the default separator for the (deprecated)
urlencoded-post method described in the XForms 1.0 spec.
http://www.w3.org/TR/xforms/slice11.html#serialize-urlencode
Earlier drafts mandated ';' as the separator, however the spec
authors eventually recognized that decision was problematic for
POST, so they allowed the separator to be configurable by the form
author to either ';' or '&'.
Allowing ';' as the separator is a good idea anyways, since
it lets future XForms authors make use of your script without
having to fuss over the choice of separator.
--
Joe Schaefer
------------------------------
Date: Mon, 26 Jul 2004 13:06:46 -0700
From: Seungbeom Kim <musiphil@bawi.org>
Subject: Re: CGI parameter separation characters
Message-Id: <ce3o8n$31s$1@news.Stanford.EDU>
Alan J. Flavell wrote:
> But the issue of using semi-colon as the alternative delimeter in
> composed GET URLs is codified in the *HTML* specifications, starting
> with RFC1866/HTML2.0. The CGI specification does not go into detail
> about the format of the QUERY_STRING, but cites other relevant
> specifications for it. With POST, on the other hand, the problem
> simply doesn't arise for which the semi-colon is the suggested
> solution, and so no solution is really needed.
The HTML 4.01 Specification still mentions only '&' as the separation
character: http://www.w3.org/TR/html4/interact/forms.html#h-17.13.4.1
Sorry for continuing this topic here, but many people have responded and
shown interest about this, so I ask for your understanding.
--
Seungbeom Kim
------------------------------
Date: Mon, 26 Jul 2004 21:29:04 +0100
From: "Alan J. Flavell" <flavell@ph.gla.ac.uk>
Subject: Re: CGI parameter separation characters
Message-Id: <Pine.LNX.4.53.0407262123430.6799@ppepc56.ph.gla.ac.uk>
On Mon, 26 Jul 2004, Seungbeom Kim wrote:
> The HTML 4.01 Specification still mentions only '&' as the separation
> character: http://www.w3.org/TR/html4/interact/forms.html#h-17.13.4.1
Sorry, you misinterpreted the context. See:
http://www.w3.org/TR/html4/appendix/notes.html#h-B.2.2
Which in effect re-iterates what it said already in RFC1866 section
8.2.1 about pre-composed query URLs (as opposed to those which are
constructed by submitting a FORM with method GET).
------------------------------
Date: Thu, 29 Jul 2004 06:13:01 GMT
From: Ron Savage <ron@savage.net.au>
Subject: CGI::Echo V 1.04
Message-Id: <I1qH61.38J@zorch.sf-bay.org>
The pure Perl module CGI::Echo V 1.04
is available immediately from CPAN,
and from http://savage.net.au/Perl-modules.html.
On-line docs, and a *.ppd for ActivePerl are also
available from the latter site.
An extract from the docs:
1.04 Mon Jul 19 10:47:00 2004
- Change Makefile.PL to coexist with Module::Build
- Rewrite t/test.t to use Test::More
--
Cheers
Ron Savage, ron@savage.net.au on 29/07/2004
http://savage.net.au/index.html
------------------------------
Date: Thu, 29 Jul 2004 06:13:24 GMT
From: Ron Savage <ron@savage.net.au>
Subject: CGI::Explorer V 2.04
Message-Id: <I1qH6B.1vMr@zorch.sf-bay.org>
The pure Perl module CGI::Explorer V 2.04
is available immediately from CPAN,
and from http://savage.net.au/Perl-modules.html.
On-line docs, and a *.ppd for ActivePerl are also
available from the latter site.
An extract from the docs:
2.04 Mon Jul 19 10:47:00 2004
- Change Makefile.PL to coexist with Module::Build
- Rewrite t/test.t to use Test::More
--
Cheers
Ron Savage, ron@savage.net.au on 29/07/2004
http://savage.net.au/index.html
------------------------------
Date: Thu, 29 Jul 2004 06:13:44 GMT
From: Ron Savage <ron@savage.net.au>
Subject: CGI::Formalware V 1.12
Message-Id: <I1qH6G.1q0n@zorch.sf-bay.org>
The pure Perl module CGI::Formalware V 1.12
is available immediately from CPAN,
and from http://savage.net.au/Perl-modules.html.
On-line docs, and a *.ppd for ActivePerl are also
available from the latter site.
An extract from the docs:
1.12 Mon Jul 19 14:10:00 2004
- Change Makefile.PL to coexist with Module::Build
- Delete ./test.pl
- Rewrite t/test.t to use Test::More
- Add t/pod.t to test all PODs
--
Cheers
Ron Savage, ron@savage.net.au on 29/07/2004
http://savage.net.au/index.html
------------------------------
Date: Thu, 29 Jul 2004 06:14:01 GMT
From: Ron Savage <ron@savage.net.au>
Subject: CGI::Session::ExpireSessions V 1.03
Message-Id: <I1qH6J.3Bz@zorch.sf-bay.org>
The pure Perl module CGI::Session::ExpireSessions V 1.03
is available immediately from CPAN,
and from http://savage.net.au/Perl-modules.html.
On-line docs, and a *.ppd for ActivePerl are also
available from the latter site.
An extract from the docs:
1.03 Mon Jul 19 14:47:00 2004
- Change Makefile.PL to coexist with Module::Build
- Add t/pod.t to test all PODs
--
Cheers
Ron Savage, ron@savage.net.au on 29/07/2004
http://savage.net.au/index.html
------------------------------
Date: Thu, 29 Jul 2004 06:14:20 GMT
From: Ron Savage <ron@savage.net.au>
Subject: CGI::Session::MembersArea V 2.01
Message-Id: <I1qH6M.1q1C@zorch.sf-bay.org>
The pure Perl module CGI::Session::MembersArea V 2.01
is available immediately from CPAN,
and from http://savage.net.au/Perl-modules.html.
On-line docs, and a *.ppd for ActivePerl are also
available from the latter site.
An extract from the docs:
2.01 Mon Jul 19 14:43:00 2004
- Change Makefile.PL to coexist with Module::Build
- Add t/pod.t to test all PODs
--
Cheers
Ron Savage, ron@savage.net.au on 29/07/2004
http://savage.net.au/index.html
------------------------------
Date: Thu, 29 Jul 2004 06:14:39 GMT
From: Ron Savage <ron@savage.net.au>
Subject: CGI::TabPane V 1.04
Message-Id: <I1qH6q.1vq7@zorch.sf-bay.org>
The pure Perl module CGI::TabPane V 1.04
is available immediately from CPAN,
and from http://savage.net.au/Perl-modules.html.
On-line docs, and a *.ppd for ActivePerl are also
available from the latter site.
An extract from the docs:
1.04 Mon Jul 19 14:43:00 2004
- Change Makefile.PL to coexist with Module::Build
- Move a few CSS declarations around between the *.css files, to help clean these files up.
You should notice nothing
- Change the default margin and padding for forms, from 0 to 5 pixels. See final.css lines 14 .. 15.
In this case, you should now notice a coloured frame around your forms
- Note: Firefox V 0.9.1 fails to properly handle the CSS required to display multiple panes stacked
vertically when the last pane is wider than the panes above it. However it does better job than
IE V 6.0.2800 at handling the width of the tab on a pane with one tab below a pane of several tabs.
You are encouraged to report all bugs to the appropriate developers
- Add t/pod.t to test all PODs
--
Cheers
Ron Savage, ron@savage.net.au on 29/07/2004
http://savage.net.au/index.html
------------------------------
Date: Sat, 24 Jul 2004 22:18:42 -0600
From: "Robin" <webmaster @ infusedlight.net>
Subject: Re: Class quandry
Message-Id: <cdvdg5$mnk$2@reader2.nmix.net>
"Andrew Burton" <tuglyraisin@aol.commcast> wrote in message
news:20040722224528.04675.00000243@mb-m21.aol.com...
> (Bah, I accidentally posted this to c.l.p.moderated. My apologies.)
>
> I'm dickering around with Perl tonight, trying to grasp OOP concepts in
Perl --
> I like them enough in C#, and thought understanding them in my favorite
> language would be worthwhile. To do this, I'm reading through and using
> examples from "Tom's object-oriented tutorial for perl." For some reason
his
> example is giving me bugs, and Google is no help. This is the error I get
with
> the following code:
> Can't modify non-lvalue subroutine call at ./testclass line 27.
>
> Here's the code...
>
> [code]
>
> #!/usr/bin/perl -w
>
> use strict;
>
> { package Roxy;
>
> sub new {
> my $self = {};
> $self->{'word'} = undef;
> bless $self;
> return $self;
> }
> sub speak {
> my $self = shift;
> print "$self says 'hello'.\n";
> }
> sub name {
> my $self = shift;
> if (@_) { $self->{'word'} = shift; }
> return $self->{'word'}
> }
> }
>
> my $muse = Roxy->new();
>
> $muse->speak;
> $muse->name = "Andy";
>
> print $muse->name;
>
> exit;
>
> [/code]
>
> For whatever it's worth, I'm using Perl 5.8.0 Any help or suggestions
would be
> appreciated. Thanks!
>
> Andrew Burton - tuglyraisin at aol dot com
> Felecia Station on Harvestgain - Jarod Godel in Second Life
was this the actual code from the example? I'm curious...
-Robin
------------------------------
Date: Sun, 25 Jul 2004 12:28:57 -0400
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: Class quandry
Message-Id: <w8ydnYhCUMJUQp7cRVn-uQ@adelphia.com>
Robin wrote:
> was this the actual code from the example? I'm curious...
If you're that curious, why not type 'perldoc perltoot' and read the
example for yourself?
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Sun, 25 Jul 2004 21:09:55 GMT
From: Joe Smith <Joe.Smith@inwap.com>
Subject: Re: Class quandry
Message-Id: <DkVMc.160272$%_6.111958@attbi_s01>
Sherm Pendley wrote:
> Robin wrote:
>> was this the actual code from the example? I'm curious...
>
> If you're that curious, why not type 'perldoc perltoot' and read the
> example for yourself?
You mean 'perldoc perlboot'.
-Joe
------------------------------
Date: Sun, 25 Jul 2004 18:32:31 -0400
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: Class quandry
Message-Id: <r7OdnW9Wl_adqJncRVn-gQ@adelphia.com>
Joe Smith wrote:
> Sherm Pendley wrote:
>
>> Robin wrote:
>>
>>> was this the actual code from the example? I'm curious...
>>
>>
>> If you're that curious, why not type 'perldoc perltoot' and read the
>> example for yourself?
>
>
> You mean 'perldoc perlboot'.
No I don't.
The OP wrote:
> To do this, I'm reading through and using
> examples from "Tom's object-oriented tutorial for perl."
That's perltoot, not perlboot.
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Mon, 26 Jul 2004 07:02:56 GMT
From: Joe Smith <Joe.Smith@inwap.com>
Subject: Re: Class quandry
Message-Id: <A02Nc.161698$%_6.100434@attbi_s01>
Sherm Pendley wrote:
>> You mean 'perldoc perlboot'.
>
>
> No I don't.
>
> The OP wrote:
>
>> To do this, I'm reading through and using
>> examples from "Tom's object-oriented tutorial for perl."
>
> That's perltoot, not perlboot.
OK, "Tom's object-oriented tutorial for perl" is perldoc perltoot.
Robin wrote: "was this the actual code from the example? I'm curious..."
The OP's sample code does not appear in perltoot but code that is
similar, with "sub speak{}", appears in perldoc perlboot.
The answer to Robin's question is: No, that is not taken verbatim
from the examples in the perl-5.8.3 docs.
-Joe
------------------------------
Date: Thu, 29 Jul 2004 06:14:55 GMT
From: Ron Savage <ron@savage.net.au>
Subject: Class::DBI::Schema2Code V 1.01
Message-Id: <I1qH6u.3Co@zorch.sf-bay.org>
The pure Perl module Class::DBI::Schema2Code V 1.01
is available immediately from CPAN,
and from http://savage.net.au/Perl-modules.html.
On-line docs, and a *.ppd for ActivePerl are also
available from the latter site.
An extract from the docs:
1.01 Mon Jul 19 14:43:00 2004
- Change Makefile.PL to coexist with Module::Build
- Add t/pod.t to test all PODs
--
Cheers
Ron Savage, ron@savage.net.au on 29/07/2004
http://savage.net.au/index.html
------------------------------
Date: Thu, 29 Jul 2004 06:15:15 GMT
From: Ron Savage <ron@savage.net.au>
Subject: Class::Tree V 1.24
Message-Id: <I1qH6x.1vqw@zorch.sf-bay.org>
The pure Perl module Class::Tree V 1.24
is available immediately from CPAN,
and from http://savage.net.au/Perl-modules.html.
On-line docs, and a *.ppd for ActivePerl are also
available from the latter site.
An extract from the docs:
1.24 Mon Jul 19 14:43:00 2004
- Change Makefile.PL to coexist with Module::Build
- Add t/pod.t to test all PODs
--
Cheers
Ron Savage, ron@savage.net.au on 29/07/2004
http://savage.net.au/index.html
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 6803
***************************************
