[18920] in Perl-Users-Digest
Perl-Users Digest, Issue: 1115 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Jun 12 03:05:46 2001
Date: Tue, 12 Jun 2001 00:05:07 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Message-Id: <992329507-v10-i1115@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Tue, 12 Jun 2001 Volume: 10 Number: 1115
Today's topics:
ANNOUNCE: Inline 0.42 <ingy@ActiveState.com>
ANNOUNCE: Inline-CPR 0.12 <ingy@ActiveState.com>
Re: Connecting to MS Access with an Apache Server??? (Mr DB)
Re: Date of Halloween (for Date::Calc module)? (Martien Verbruggen)
Re: ENV{HTTP_REFERER} in Netscape (Tim Hammerquist)
Re: Getting the First Letter in string <pne-news-20010612@newton.digitalspace.net>
Re: Getting the First Letter in string <pne-news-20010612@newton.digitalspace.net>
Guten Editor fuer Windows <jsommer@my-deja.com>
Re: Guten Editor fuer Windows <jsommer@my-deja.com>
Re: Guten Editor fuer Windows (Bernard El-Hagin)
Re: Limiting special characters <pne-news-20010612@newton.digitalspace.net>
Re: Limiting special characters <pne-news-20010612@newton.digitalspace.net>
Re: Simplest code to test if web site is up? <pne-news-20010612@newton.digitalspace.net>
Re: The FlakeyMind Thaddes FAQ (v0.1) <Attila.Feher@lmf.ericsson.se>
Re: The meaning of $#, $/, and $* <pne-news-20010612@newton.digitalspace.net>
Re: The meaning of $#, $/, and $* (Craig Berry)
Re: The meaning of $#, $/, and $* <pne-news-20010612@newton.digitalspace.net>
Re: The meaning of $#, $/, and $* (Bernard El-Hagin)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 12 Jun 2001 05:14:33 GMT
From: Brian Ingerson <ingy@ActiveState.com>
Subject: ANNOUNCE: Inline 0.42
Message-Id: <3B25177E.3020806@ActiveState.com>
INTRODUCTION:
Inline.pm - Write Perl subroutines in other programming languages.
Inline lets you write Perl subroutines in other programming languages
like C, C++, Java, Python, Tcl and even Assembly. You don't need to
compile anything. All the details are handled transparently so you
can just run your Perl script like normal.
Example:
use Inline::Files;
use Inline C;
print JAxH('Inline'), "\n";
__C__
SV* JAxH(char* x) {
return newSVpvf ("Just Another %s Hacker",x);
}
When run, this complete program prints:
Just Another Inline Hacker
The one line version is:
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf("Just
Another %s Hacker",x);}};print JAxH+Inline'
-------------------------------------------------------------------------------
FEATURES:
Inline version 0.42 is a minor release:
+ Applied a couple patches. Python and Tcl now install properly.
Inline version 0.41 is a minor release:
+ Added the AUTOWRAP feature for C
- Inline can now create wrappers from C function *declarations* alone.
+ Made Inline::MakeMaker work correctly in nested Makefile.PL trees.
+ Fixed bug preventing other Inline::* modules from installing in some
cases.
+ Fixed platform dependent CRLF issues.
Inline version 0.40 is a major upgrade. It includes:
+ Inline::MakeMaker
+ Rock solid support for writing CPAN extension modules
+ Short file names.
+ No more
_Inline/lib/auto/Foo_C_3cee729d1d942c6792ca5a741dc21879/Foo_C_3cee729d1d942c6792ca5a741dc21879.so
+ Now it's _Inline/lib/auto/Foo/Foo.so
+ Support for creating binary distributions.
+ Can even do it without shipping C source code.
+ Support for Damian Conway's Inline::Files
+ No more __END__ markers.
+ Safe new config and caching format.
+ Similar to Data::Denter format
+ New Inline-FAQ.pod.
Inline version 0.34 fixes 2 minor bugs:
+ Makefile.PL got confused on $Config::Config{cc} with full pathnames or
flags
+ Makefile.PL/Makefile dependency caused a problem in one rare case.
Inline version 0.33 is a minor upgrade with the following changes:
+ Support for Inline::Struct and Inline::Filters
+ Added ENABLE and DISABLE configuration modifiers.
+ C installation is optional
+ Test harness reworked. Faster testing.
+ Fixed all reported (and some unreported) bugs.
+ Documentation enhancements.
Inline version 0.32 is a minor upgrade with the following changes:
+ Addition of UNTAINT, SAFEMODE, GLOBAL_LOAD, MAKE, and LDDLFLAGS
configuration options.
+ Fixed all reported (and some unreported) bugs.
+ Documentation enhancements.
Inline version 0.31 is a minor upgrade with the following changes:
+ "use Inline C;" is now a synonym for "use Inline C => DATA;"
+ Default build/install directory changed from "blib_I/" to ".Inline/"
+ Build/Install directory structure simplified.
+ Short install paths.
+ Build areas in ".Inline/build/" subdirectory.
+ Added 'CC', 'CCFLAGS', 'LD', and 'LDFLAGS' config options to C.
+ More recipes in Cookbook.
Inline version 0.30 is a major upgrade from previous verions. It includes:
+ Integrated support for typemap files in C.
+ All the recognized types now come *only* from typemaps.
+ The default types come from the default typemap installed with core
Perl.
+ Typemaps are used to modify the Parse::RecDescent grammar for
parsing C.
+ This means you can easily use your existing typemaps.
+ Language support completely separated from base Inline code.
+ Beta supoort for C (Inline::C, included)
+ Alpha support for C++ (Inline::CPP, available separately)
+ Alpha support for Python (Inline::Python, available separately)
+ Support for 'embedding' Perl in C with my new programming language,
CPR.
(Inline::CPR, available separately) This one may warp your mind :^)
+ Simple API for adding your own language support.
+ Write your own Inline::Foo
+ Write your own implementation of Inline::C, or just modify
Inline::C::grammar.
+ Support for interpreted languages in addition to compiled ones.
+ Autodetection of new Inline language modules.
+ Much easier and more powerful configuration syntax.
+ More XS and MakeMaker features exposed for configuration (for C and
C++).
+ Flexible new syntax for specifying source code.
+ Use DATA section for AutoLoader, Inline, and POD simultaneously.
+ Support for using Inline 'with' other modules.
+ "use Inline with 'Event';" lets Event.pm pass config info to Inline.pm.
+ Event.pm 0.80 has built in support for Inline.pm 0.30 and higher.
+ Write Event callbacks in C with extreme ease.
+ More documentation
+ perldoc Inline
+ perldoc Inline-FAQ
+ perldoc Inline-API
+ perldoc Inline::C
+ perldoc Inline::C-Cookbook
+ Better error messages and easier debugging.
+ Mailing list: inline@perl.org
Other features of Inline.pm include:
= Automatically compiles your source code and caches the shared object.
= Automatically DynaLoads the shared object and binds it to Perl.
= Recompiles only when the C code changes.
= Changing the Perl code will not cause a recompile of the C code.
= Support for writing extension modules, suitable for distributing to
the CPAN.
= Support for generating and binding Inline subs at run time. <bind()>
= Works on all Unix and MS Windows configurations.
-------------------------------------------------------------------------------
INSTALLATION:
This module requires the Digest::MD5 and Parse::RecDescent modules. It also
requires the appropriate C compiler. (Where appropriate means the one
referred
to in your Config.pm)
To install Inline do this:
perl Makefile.PL
make
make test
make install
On ActivePerl for MSWin32, use nmake instead of make. Or just use:
ppm install Inline
For convenience, Inline::C is packaged with Inline, and will be
automatically
installed as well.
-------------------------------------------------------------------------------
INFORMATION:
= For more information on Inline, see 'perldoc Inline' and 'perldoc
Inline-FAQ'
= For information about Inline::, see 'perldoc Inline::C' and
'perldoc Inline::C-Cookbook'
= For information on writing your own Inline extension see 'perldoc
Inline-API'
= For information about the Perl5 internal C API, see 'perldoc perlapi' or
try http://www.perldoc.com/perl5.6/pod/perlapi.html
= The Fall 2000 edition of The Perl Journal has an article about Inline
The Inline.pm mailing list is inline@perl.org. Send email to
inline-subscribe@perl.org to subscribe.
Please send questions and comments to "Brian Ingerson" <INGY@cpan.org>
Copyright (c) 2001, Brian Ingerson. All Rights Reserved.
------------------------------
Date: Mon, 11 Jun 2001 19:09:26 GMT
From: Brian Ingerson <ingy@ActiveState.com>
Subject: ANNOUNCE: Inline-CPR 0.12
Message-Id: <3B2517C5.2050401@ActiveState.com>
INTRODUCTION:
CPR - C Perl Run
A Perl interpreter 'embedded' in your C?
A C interpreter using Perl?
A new API for the Perl5 internals?
Welcome to the wacky world of CPR!
To take a test drive, just put a CPR hashbang at the top of your C program
and run it like a Perl script.
Here is an example:
#!/usr/bin/cpr
/* hello.cpr - Just say "Hello" */
int main(void) {
printf("Hello, world\n");
return 0;
}
Or (if your chitty hashbang is out for repairs) just run:
cpr hello.cpr
After a few seconds, your CPR program will greet the Earth in the standard
fashion. Run it again for a faster response.
-------------------------------------------------------------------------------
FEATURES:
Inline::CPR version 0.12 is a minor release:
+ Made compatible with Inline 0.42
-------------------------------------------------------------------------------
INSTALLATION:
This module requires Inline.pm version 0.30 or higher, and the appropriate
C compiler. (Where appropriate means the one referred to in your Config.pm)
To install Inline::CPR do this:
perl Makefile.PL
make
make test
make install
(On ActivePerl for MSWin32, use nmake instead of make.)
This will not only install Inline::CPR, but will also install a binary
program: 'cpr'. This is the CPR interpreter. Inline::CPR is just a support
module for the CPR interpreter. (You don't actually use it directly.)
The installation process will also generate a sample CPR program:
./examples/synopsis.cpr
You have to 'make install' before you can run it successfully.
-------------------------------------------------------------------------------
INFORMATION:
- For more information on CPR, see 'perldoc Inline::CPR'.
- For information about Inline.pm, see 'perldoc Inline'.
- For information about the Perl5 internal C API, see 'perldoc perlapi' or
try http://www.perldoc.com/perl5.6/pod/perlapi.html
The CPR mailing list is inline@perl.org. Send mail to
inline-subscribe@perl.org
to subscribe.
Please send questions and comments to "Brian Ingerson" <INGY@cpan.org>
Copyright (c) 2001, Brian Ingerson. All Rights Reserved.
------------------------------
Date: 11 Jun 2001 21:51:26 -0700
From: mrdbsql@yahoo.com (Mr DB)
Subject: Re: Connecting to MS Access with an Apache Server???
Message-Id: <7ad1b2de.0106112051.180c0e17@posting.google.com>
"Ryan" <ryan@tuitions.com> wrote in message news:<9duv5t$ajf$1@news.xmission.com>...
> Our web site is running on an remote apache server and we have a MS access
> database that we would like copy up to a directory and to be able to simply
> exctract information from and show it in an HTML format.
If your need is to get the data from an Access MDB file onto a
website, then one quick (and secure) way to do this is via some
Application Service Provider site that specializes in this type of
service. E.g., bitlocker.com was one that puts data on a website, but
they just died.
Another up and coming site, far more sophisticated, is
http://www.westside.com. You just point it at your mdb and it loads up
the data, mirrors the table relationships, builds a default set of
forms (including support for any lookup tables you might have had) and
you're set. By default they provide updating, but it sounds like you
just need to view the data so you'll need to turn off the update
buttons (trivial). Security is typical web-style. "Invite" via email
and they get a password to logon with. You can either allow or
disallow access to anonymous users (disallow by default).
Oh, and its free for the first 60 days, so it won't cost you to try
this (they have an in-house option too). I've used their site for
several non-profits and it makes me look like a star when all of
sudden their mailing list (typically :->) is "on the web". (Free
hosting for typical non-profits doesn't hurt either...)
Hope this helps...
------------------------------
Date: Tue, 12 Jun 2001 04:07:07 GMT
From: mgjv@tradingpost.com.au (Martien Verbruggen)
Subject: Re: Date of Halloween (for Date::Calc module)?
Message-Id: <slrn9ib5bb.f15.mgjv@verbruggen.comdyn.com.au>
On 09 Jun 2001 07:00:10 -0700,
Randal L. Schwartz <merlyn@stonehenge.com> wrote:
>>>>>> "Damian" == Damian James <damian@qimr.edu.au> writes:
>
>Damian> Damian
>Damian> [Who will be a face in the crowd for Randal
>Damian> at SAGE-AU in Adelaide this July]
>
> Sheesh, is every Perl programmer in Oz named Damian? Is this some
> sort of new rule?
Not every one.
I'll try to be there as well, but I'm not sure yet whether I'll be
able to make it this year.
Martien
--
Martien Verbruggen |
Interactive Media Division | "In a world without fences,
Commercial Dynamics Pty. Ltd. | who needs Gates?"
NSW, Australia |
------------------------------
Date: Tue, 12 Jun 2001 04:22:10 GMT
From: tim@vegeta.ath.cx (Tim Hammerquist)
Subject: Re: ENV{HTTP_REFERER} in Netscape
Message-Id: <slrn9ib6qp.4r8.tim@vegeta.ath.cx>
Dianne van Dulken <dianne@dogmac.com> wrote:
> I have already posted this to the perl and perl-cgi mailing lists, but
> haven't been able to find a solution
>
> I am calling a perl script from a HTML page in the following form:
>
> <script language="javascript"
> src="https://testserver.com.au/server/cgi-bin/script1.pl">
>
> This checks the HTTP_REFERER of the calling page, and if it is one we like,
> gives one set of javascript back, or else a different set.
>
> The problem is that Netscape isn't giving me a HTTP_REFERER code at all..
> Everyone I have talked to agrees that it SHOULD be giving it to me, but in
> none of our tests it has done so.
>
> Has anyone got a suggestion of what else I could use? The javascript
> http_referrer still works in Netscape, but not the perl version. We need to
> find the IP of the page calling the code, not the users IP or anything like
> that.
I threw together a quick hack that will let you peek at the headers
being sent to the perl script impersonating a javascript src file. Try
plugging this in:
: #!/usr/bin/perl -w
:
: use strict;
: use CGI;
:
: my $q = new CGI;
:
: open LOG, "> /path/to/log.txt" or die "can't open log file";
:
: for (sort keys %ENV) {
: my $pair;
:
: $pair = "$_ = $ENV{$_}";
: print LOG "$pair\n";
:
: print "document.write('<BR>" . $q->escapeHTML($pair) . "');\n";
: }
:
: close LOG;
The log is to verify what's getting sent. Make sure it's writable by
the server. This will just dump all the server variables to the browser
window.
By using this I found that the HTTP_REFERER var is only sent (on
Netscape 4.73 on Mandrake Linux 7.1) when a URI is called through an
HTML anchor tag. It's not passed when a URI is entered directly on the
Location bar, nor is it passed to javascript source files. I thought I
remembered this from about a year ago working with CGI env vars, but I
had to make sure.
(tested on Mandrake Linux 7.1 with Apache 1.3.12 with
mod_perl/Apache::ASP/Perl 5.6 and Netscape Navigator 4.73)
I have to run now, but I hope the above script can help you figure out
what's going on, and hopefully lead to a solution.
HTH
--
-Tim Hammerquist <timmy@cpan.org>
The surest sign that intelligent life exists elsewhere in
the universe is that it has never tried to contact us.
-- Bill Watterson (Calvin & Hobbes)
------------------------------
Date: Tue, 12 Jun 2001 06:55:05 +0200
From: Philip Newton <pne-news-20010612@newton.digitalspace.net>
Subject: Re: Getting the First Letter in string
Message-Id: <oi7bitsof8dsjfv7avio1u2f6v63np01no@4ax.com>
On Mon, 11 Jun 2001 16:41:53 +0500, Robert Sherman
<rsherman@ce.gatech.edu> wrote:
> $name =~ /^\w{1}/;
You don't need the {1} if you're only interested in one alphanumunder
char.
> $initial= $&;
This will, of course, slow down every other regular expression in the
script, even if it does no capturing. *If* you're going to use a regex,
then something like
$name =~ /^(.)/s && $initial = $1;
would probably bet better. Firstly, because this matches any character
(not just alphanumunders), and secondly, because it doesn't use any of
$` $& $' when $1 is just as easy to use. (If you want the first
alphanumunder in the string, use /(\w)/ instead of /^(.)/s.)
I still prefer the substr version.
Cheers,
Philip
--
Philip Newton <nospam.newton@gmx.li>
That really is my address; no need to remove anything to reply.
If you're not part of the solution, you're part of the precipitate.
------------------------------
Date: Tue, 12 Jun 2001 06:55:06 +0200
From: Philip Newton <pne-news-20010612@newton.digitalspace.net>
Subject: Re: Getting the First Letter in string
Message-Id: <dp7bitca9cemhhf7friovt89e6l4vf2aor@4ax.com>
On 11 Jun 2001 23:32:35 -0400, Joe Schaefer <joe+usenet@sunstarsys.com>
wrote:
> $first = unpack a => $str;
> $first = pack a => $str;
Nice symmetry.
> $first = chr ord $str;
I like this one, too ;-)
Thanks for the input!
Cheers,
Philip
--
Philip Newton <nospam.newton@gmx.li>
That really is my address; no need to remove anything to reply.
If you're not part of the solution, you're part of the precipitate.
------------------------------
Date: Tue, 12 Jun 2001 06:21:43 GMT
From: "Juerg Sommer" <jsommer@my-deja.com>
Subject: Guten Editor fuer Windows
Message-Id: <XxiV6.90$io1.489949@news>
Hallo zusammen
Ich suche schon seit längerem einen guten Editor für Windows, der folgende
Anforderungen erfüllt:
- Syntax-Highlighting (der auch mit " und \" korrekt umgehen kann, also
print "Dies ist \"ein\" test"; korrekt darstellen kann)
- Klammern-Spring-Funktion wie das % beim vi
- Speicherformat UNIX und MS-DOS
- Zeilennummern
- nicht zu teuer (max. 50$). Ich denke aber, dass es auch eine gute Freeware
gibt.
Ich habe mir schon vor längerer Zeit einmal eine Vollversion von Text-Pad
geleistet (http://www.textpad.com), da der viele von mir benötigten
Programmiersprachen (Perl/CGI, PHP, HTML, Pascal und C) recht gut darstellt.
Leider kann er \" nicht von " unterscheiden, so dass ich häufig einige
Zeilen Code habe, die als reinen Text erkannt werden. Zudem vermisse ich das
VI-%, so dass ich immer wieder zwischen Text-Pad und VIM wechseln muss. VIM
wäre zwar gut, was das Syntax-Highlighting anbelangt (und das % erst recht),
ist mir aber auf die Dauer wirklich zu umständlich (aber das ist wieder eine
andere Sache)...
Kennt jemand ein gutes Tool?
Danke und Gruss
Jürg
------------------------------
Date: Tue, 12 Jun 2001 06:31:27 GMT
From: "Juerg Sommer" <jsommer@my-deja.com>
Subject: Re: Guten Editor fuer Windows
Message-Id: <3HiV6.91$io1.489965@news>
sorry, wrong newsgroup...
------------------------------
Date: Tue, 12 Jun 2001 06:32:17 +0000 (UTC)
From: bernard.el-hagin@lido-tech.net (Bernard El-Hagin)
Subject: Re: Guten Editor fuer Windows
Message-Id: <slrn9ibd3v.k93.bernard.el-hagin@gdndev25.lido-tech>
On Tue, 12 Jun 2001 06:31:27 GMT, Juerg Sommer <jsommer@my-deja.com> wrote:
>sorry, wrong newsgroup...
Jawohl, mein Herr. :-)
Cheers,
Bernard
--
perl -l54e's yyw q q tvmrx "h\ywx ersxliv zivp legoiv"qiy;y #a-zA-Z#d-gu-z#
chefghijklmnopqrstuvwxyzcJab-def-uPwxyzc;s j j s u u s t t s r r s
ppevalpereeteueje'
------------------------------
Date: Tue, 12 Jun 2001 06:55:07 +0200
From: Philip Newton <pne-news-20010612@newton.digitalspace.net>
Subject: Re: Limiting special characters
Message-Id: <5s7bitcj09lm8aded8bdco1kt9ga0dl6c7@4ax.com>
On Tue, 12 Jun 2001 00:00:58 GMT, "John W. Krahn" <krahnj@acm.org>
wrote:
> This is a C (or C++) program example. The perl equivalent would be:
>
> $data =~ s#[^0-9a-zA-Z!@%_=+:,./-]#_#
Or
$data =~ tr#0-9a-zA-Z!@%_=+:,./-#_#c;
Cheers,
Philip
--
Philip Newton <nospam.newton@gmx.li>
That really is my address; no need to remove anything to reply.
If you're not part of the solution, you're part of the precipitate.
------------------------------
Date: Tue, 12 Jun 2001 06:55:08 +0200
From: Philip Newton <pne-news-20010612@newton.digitalspace.net>
Subject: Re: Limiting special characters
Message-Id: <q18bit8k01jgpdl4jf2cs17002217pdita@4ax.com>
On Tue, 12 Jun 2001 00:47:18 +0100, "David Soming"
<davsoming@lineone.net> wrote:
> if ($message =~ /($+[?|()[\]{}^*.<])/) {
^^
I don't think you really want the variable $+ in there.
Cheers,
Philip
--
Philip Newton <nospam.newton@gmx.li>
That really is my address; no need to remove anything to reply.
If you're not part of the solution, you're part of the precipitate.
------------------------------
Date: Tue, 12 Jun 2001 06:55:04 +0200
From: Philip Newton <pne-news-20010612@newton.digitalspace.net>
Subject: Re: Simplest code to test if web site is up?
Message-Id: <ic7bitgfc5u7mlckevagttr277ab94p92f@4ax.com>
On Tue, 12 Jun 2001 01:24:19 +0200, "Willem" <usenet@willem.byte.nl>
wrote:
> Use IO::Socket (std module) and send "HEAD / HTTP/1.0\n\n" to the server. If
> you get a response, it is working :-)
Not necessarily, as the virtual host translation might be broken and you
didn't send a Host: header.
Off-topic, so Followup-to: poster set.
Cheers,
Philip
--
Philip Newton <nospam.newton@gmx.li>
That really is my address; no need to remove anything to reply.
If you're not part of the solution, you're part of the precipitate.
------------------------------
Date: Tue, 12 Jun 2001 08:22:14 +0300
From: Attila Feher <Attila.Feher@lmf.ericsson.se>
Subject: Re: The FlakeyMind Thaddes FAQ (v0.1)
Message-Id: <3B25A706.BF747286@lmf.ericsson.se>
Topmind wrote:
>
> > Topmind wrote:
> > >
> > >
> > > > So if U R fed up with a stupid manager: go and convince him!
> > >
> > > They don't have the attention span. They get their info
> > > from airline mags. If the airline mag says so.....
> > >
> > > > Go away from here, U won't find your demons here.
> > >
> > > BS and distortion and hype == enemy
> > >
> > > -T-
> >
> > You _are_ paranoid. GET LOST!
> >
>
> I might be paranoid, but you are obviously
> highly irritable.
I play to be. That is the diff :-)))
> Perhaps we can make a mutual deal to get
> treatment.
No THX. No need here. For me it is a game.
A
------------------------------
Date: Tue, 12 Jun 2001 06:55:04 +0200
From: Philip Newton <pne-news-20010612@newton.digitalspace.net>
Subject: Re: The meaning of $#, $/, and $*
Message-Id: <9f7bitg4m49jdrht03nur3l23g8jfnojnn@4ax.com>
On Mon, 11 Jun 2001 21:27:40 -0000, cberry@cinenet.net (Craig Berry)
wrote:
> I'm hoping if I (and others) suggest it often enough,
> one of the Great Old Ones may decide to implement the idea.
I don't think the Backward Compatibility Police would let it through
(disregarding for now that it's probably next to impossible to estimate
how much $# is in use in old code).
Cheers,
Philip
--
Philip Newton <nospam.newton@gmx.li>
That really is my address; no need to remove anything to reply.
If you're not part of the solution, you're part of the precipitate.
------------------------------
Date: Tue, 12 Jun 2001 05:53:09 -0000
From: cberry@cinenet.net (Craig Berry)
Subject: Re: The meaning of $#, $/, and $*
Message-Id: <tibbi5b6e3qk68@corp.supernews.com>
Philip Newton (pne-news-20010612@newton.digitalspace.net) wrote:
: On Mon, 11 Jun 2001 21:27:40 -0000, cberry@cinenet.net (Craig Berry)
: wrote:
:
: > I'm hoping if I (and others) suggest it often enough,
: > one of the Great Old Ones may decide to implement the idea.
:
: I don't think the Backward Compatibility Police would let it through
: (disregarding for now that it's probably next to impossible to estimate
: how much $# is in use in old code).
Note that it could behave the old way when set, and the new way when read.
I'm sure a tiny fraction of the scripts using $# ever read its value.
--
| Craig Berry - http://www.cinenet.net/~cberry/
--*-- "God becomes as we are that we may be as he is."
| - William Blake
------------------------------
Date: Tue, 12 Jun 2001 08:12:30 +0200
From: Philip Newton <pne-news-20010612@newton.digitalspace.net>
Subject: Re: The meaning of $#, $/, and $*
Message-Id: <vkcbitkh7j6fotr366k100oaf7705mnupa@4ax.com>
On Tue, 12 Jun 2001 05:53:09 -0000, cberry@cinenet.net (Craig Berry)
wrote:
[$#]
> Note that it could behave the old way when set, and the new way when read.
> I'm sure a tiny fraction of the scripts using $# ever read its value.
E2MUCHMAGIC. Try explaining *that* behaviour to a beginner :-)
(Maybe possible, but I still doubt that'll fly ;-)
Cheers,
Philip
--
Philip Newton <nospam.newton@gmx.li>
That really is my address; no need to remove anything to reply.
If you're not part of the solution, you're part of the precipitate.
------------------------------
Date: Tue, 12 Jun 2001 06:21:03 +0000 (UTC)
From: bernard.el-hagin@lido-tech.net (Bernard El-Hagin)
Subject: Re: The meaning of $#, $/, and $*
Message-Id: <slrn9ibcep.k93.bernard.el-hagin@gdndev25.lido-tech>
On 11 Jun 2001 20:50:35 GMT, Anno Siegel <anno4000@lublin.zrz.tu-berlin.de>
wrote:
>According to Craig Berry <cberry@cinenet.net>:
>
>> By the way, I've been agitating for a couple of years to repurpose $# to
>> hold the current index value within a foreach construct, but don't seem to
>> be making much headway.
>
>If you hadn't mentioned it, I would have. I am much in favor of the
>resurrection of $# in this form.
Hey man, my JAPH would stop working! :-)
Cheers,
Bernard
--
perl -le '$#="Just another Perl hacker,";print print'
------------------------------
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.
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 1115
***************************************
