[29278] in Perl-Users-Digest
Perl-Users Digest, Issue: 522 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Jun 16 06:09:51 2007
Date: Sat, 16 Jun 2007 03:09:05 -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 Sat, 16 Jun 2007 Volume: 11 Number: 522
Today's topics:
Re: Massive Memory Structures ruu@cwcom.net
Re: Massive Memory Structures <tadmc@seesig.invalid>
Re: Massive Memory Structures <rvtol+news@isolution.nl>
new CPAN modules on Sat Jun 16 2007 (Randal Schwartz)
Re: Perl script to identify corrupt mbox messages? <rvtol+news@isolution.nl>
Re: Perl script to identify corrupt mbox messages? <tuxedo@mailinator.net>
Re: Perl script to identify corrupt mbox messages? <rvtol+news@isolution.nl>
Re: Perl script to identify corrupt mbox messages? <tuxedo@mailinator.net>
Re: Perl script to identify corrupt mbox messages? <hjp-usenet2@hjp.at>
Re: Perl script to identify corrupt mbox messages? <paduille.4061.mumia.w+nospam@earthlink.net>
Re: Perl script to identify corrupt mbox messages? <tuxedo@mailinator.net>
Re: perl vs C for CGI <tadmc@seesig.invalid>
Re: question about sorting syntax <minimiscience+usenet@gmail.com>
Re: question about sorting syntax <mritty@gmail.com>
Re: question about sorting syntax <jgibson@mail.arc.nasa.gov>
Re: simple regex <regis44@gmail.com>
Re: Template <glex_no-spam@qwest-spam-no.invalid>
Re: Template <tadmc@seesig.invalid>
Re: Template <rvtol+news@isolution.nl>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 15 Jun 2007 15:59:40 -0700
From: ruu@cwcom.net
Subject: Re: Massive Memory Structures
Message-Id: <1181948380.781819.311060@q75g2000hsh.googlegroups.com>
On Jun 15, 2:28 pm, jgra...@ti.com wrote:
> r...@cwcom.net writes:
> > No-one knows? Not even a "if you have to use more than 4G of memory,
> > you don't know what you are doing" reply?
> > Dave
>
> > On Jun 13, 4:44 pm, r...@cwcom.net wrote:
> > > OK - I was under the impression that perl running on a 64 bit OS,
> > > compiled for said 64 bit OS would be able to handle data structures in
> > > memory greater than 4G in size. I've tried this with a couple of OS's
> > > (Solaris on sparc, Solaris on x86_64) with both packaged and compiled
> > > versions of perl with identical results - as soon as I hit 4G with my
> > > script, I get an out of memory error and the script dies.
>
> > > I'm pretty sure I don't have a ulimit issue, since more or less
> > > everything is unlimited, and other programs run by the same user can
> > > access over 4G of ram quite happily.
>
> > > Two questions:
>
> > > 1) Is it possible to access a structure over 4G with perl running on
> > > Solaris?
> > > 2) If so, what options do I need to compile in to make this happen.
>
> > > Dave
>
> Possibly if you follow the steps in the posting guidelines,
> such as posting a runnable short program that demonstrates the problem,
> your post will both overcome the work-threashold-limit
> and also pass the "sounds interesting" threshold
> so that one of the few people here who have not only
> the knowledge, ability, experience, but also the resource (4G solaris machine)
> to check it out on their system, and if it works, to post their configuration.
>
> Our workgroup has been moving away from Solaris boxes
> and toward Linux running on AMD Opterons, for 4G/8G/16G memory setups,
> so even if you posted an example, I wouldn't have the ability to try it on
> a suitable Solaris machine.
>
> --
> Joel
OK. Sounds fair. If you feel like running this on a Linux system, I
would be interested to know if it works or not, even if it isnt
Solaris.
Below is a short script that works under Solaris (and probably
anything that has mkfile). It will create a 5g test file, and then
attempt to pull the whole thing into $bigvar. You will need to have
enough space somewhere to create the 5G file, and at least 8G of RAM
to attempt. Please, anyone reading this, DO NOT RUN THIS SCRIPT IF
YOU ARENT SURE WHAT IT WILL DO, OR ON A PRODUCTION SYSTEM - there is a
reasonable chance that your OS may fail in exciting ways if it uses up
all of the memory. Further rules:
1) Please dont run the script if you manage the safety systems of a
nuclear power station.
2) Please dont run the script on anything labelled "life support"
3) If you work in a lab, have played "Far Cry", and thought "This
looks familiar" at any point during the game, please dont run the
script.
#!/usr/bin/perl
$filename = shift || die("Need to be passed a test file.\n");
`/usr/sbin/mkfile 5g $filename`;
unless (-s "$filename") {
die("Failed to create testfile $filename.\n");
}
open(FILE,"$filename");
$bigvar = <FILE>;
close FILE;
print "I successfully read in the test file.\n";
unlink($filename) || die("Failed to remove test file $filename.\n");
Dave
------------------------------
Date: Fri, 15 Jun 2007 18:22:34 -0500
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: Massive Memory Structures
Message-Id: <slrnf767pq.mbs.tadmc@tadmc30.sbcglobal.net>
ruu@cwcom.net <ruu@cwcom.net> wrote:
> I got a perl error
Can you find the (mystery) error message in perldiag.pod?
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Sat, 16 Jun 2007 02:38:53 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: Massive Memory Structures
Message-Id: <f4vik5.10o.1@news.isolution.nl>
ruu@cwcom.net schreef:
> open(FILE,"$filename");
> $bigvar = <FILE>;
> close FILE;
Why not create the $bigvar directly?
#!/usr/bin/perl
use strict;
use warnings;
my $b = '#' x 128;
my $n = 0;
while ($n < 3_000_000_000) {
$b .= $b;
print $n = length $b, "\n";
}
__END__
See also `perl -V:* |grep 32`, and try 64 too.
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: Sat, 16 Jun 2007 04:42:14 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Sat Jun 16 2007
Message-Id: <JJpp2E.2z4@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Bio-DOOP-DOOP-0.25
http://search.cpan.org/~tibi/Bio-DOOP-DOOP-0.25/
DOOP API main module
----
Bundle-Complete-Catalyst-0.01
http://search.cpan.org/~ski/Bundle-Complete-Catalyst-0.01/
installs all Catalyst modules
----
Calendar-Japanese-Holiday-0.02
http://search.cpan.org/~kztomita/Calendar-Japanese-Holiday-0.02/
Japanese holidays in calender
----
Catalyst-Model-CacheFunky-Loader-0.03
http://search.cpan.org/~tomyhero/Catalyst-Model-CacheFunky-Loader-0.03/
Load Cache::Funky Modules.
----
Catalyst-Model-CacheFunky-Loader-0.04
http://search.cpan.org/~tomyhero/Catalyst-Model-CacheFunky-Loader-0.04/
Load Cache::Funky Modules.
----
DBI-1.56_92
http://search.cpan.org/~timb/DBI-1.56_92/
Database independent interface for Perl
----
DBIx-FileSystem-1.2
http://search.cpan.org/~afrika/DBIx-FileSystem-1.2/
Manage tables like a filesystem
----
DBIx-MyServer-0.20
http://search.cpan.org/~philips/DBIx-MyServer-0.20/
Server-side implementation of the MySQL network protocol
----
DashProfiler-1.01
http://search.cpan.org/~timb/DashProfiler-1.01/
collect call count and timing data aggregated by context
----
Devel-PDB-0.05
http://search.cpan.org/~ivanwong/Devel-PDB-0.05/
A simple Curses-based Perl Debugger
----
Egg-Release-2.13
http://search.cpan.org/~lushe/Egg-Release-2.13/
Version of Egg WEB Application Framework.
----
Eludia-07.06.15
http://search.cpan.org/~dmow/Eludia-07.06.15/
----
Geo-Query-LatLong-0.8002
http://search.cpan.org/~retoh/Geo-Query-LatLong-0.8002/
Perl module to query latitude and longitude from a city.
----
Log-Handler-0.36
http://search.cpan.org/~bloonix/Log-Handler-0.36/
A simple handler to log messages to log files.
----
Net-OICQ-1.5
http://search.cpan.org/~tangent/Net-OICQ-1.5/
Perl extension for QQ instant messaging protocol
----
Regexp-Wildcards-0.01
http://search.cpan.org/~vpit/Regexp-Wildcards-0.01/
Converts wildcards expressions to Perl regular expressions.
----
Search-Xapian-1.0.1.0
http://search.cpan.org/~olly/Search-Xapian-1.0.1.0/
Perl XS frontend to the Xapian C++ search library.
----
Tie-File-FixedRecLen-0.3
http://search.cpan.org/~oliver/Tie-File-FixedRecLen-0.3/
Fixed Length Record support for Tie:File
----
XML-Bare-0.04
http://search.cpan.org/~codechild/XML-Bare-0.04/
Minimal XML parser implemented via a C++ state engine
----
onto-perl-0.32
http://search.cpan.org/~easr/onto-perl-0.32/
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: Sat, 16 Jun 2007 00:00:20 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: Perl script to identify corrupt mbox messages?
Message-Id: <f4v9c8.1c4.1@news.isolution.nl>
Tuxedo schreef:
> [attribution repaired] Ruud:
>> Consider formail, it is on about every *ix system.
>
> Sounds good but unfortunately the mbox belongs to a company which
> would not consider anything better than their crap Windows system!
Well, you could still move the file to a different system, or add
cygwin.
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: Sat, 16 Jun 2007 00:40:05 +0200
From: Tuxedo <tuxedo@mailinator.net>
Subject: Re: Perl script to identify corrupt mbox messages?
Message-Id: <f4v4g5$8kj$01$1@news.t-online.com>
Dr.Ruud wrote:
> Tuxedo schreef:
> > [attribution repaired] Ruud:
>
> >> Consider formail, it is on about every *ix system.
> >
> > Sounds good but unfortunately the mbox belongs to a company which
> > would not consider anything better than their crap Windows system!
>
> Well, you could still move the file to a different system, or add
> cygwin.
>
True, but the file still needs to be parsed by the Mozilla application
running on a Windows system. In fact, the exact same error occurs on a
Linux system when placing the mbox in the Mozilla mail directory.
------------------------------
Date: Sat, 16 Jun 2007 02:40:56 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: Perl script to identify corrupt mbox messages?
Message-Id: <f4vik6.10o.1@news.isolution.nl>
Tuxedo schreef:
> Dr.Ruud:
>> Tuxedo:
>>> [attribution repaired] Ruud:
>>>> Consider formail, it is on about every *ix system.
>>>
>>> Sounds good but unfortunately the mbox belongs to a company which
>>> would not consider anything better than their crap Windows system!
>>
>> Well, you could still move the file to a different system, or add
>> cygwin.
>
> True, but the file still needs to be parsed by the Mozilla application
> running on a Windows system. In fact, the exact same error occurs on a
> Linux system when placing the mbox in the Mozilla mail directory.
Use formail to repair the file, is why I suggested it.
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: Sat, 16 Jun 2007 09:24:05 +0200
From: Tuxedo <tuxedo@mailinator.net>
Subject: Re: Perl script to identify corrupt mbox messages?
Message-Id: <f5036l$c9o$00$1@news.t-online.com>
Dr.Ruud wrote:
[...]
> Use formail to repair the file, is why I suggested it.
>
My mistake, and thanks for the tip! I was not familiar with 'formail'
before. This interesting utility is indeed is on my Linux system. But
having neither a remote idea what error(s) the original mailbox may
contain, nor being familiar with formail, it is a bit complicated to guess
how to best process it. Nevertheless, I tried the following examples:
formail -ds <my_crappy_mbox >>reinvigorated_mbox
... this certainly made some changes, in fact, 10 or so additional messages
appear in the Mozilla index which did not show up earlier, including a
couple without a valid sender which are now listed by Mozilla as from
foo@bar, but which appear to be file fragments, i.e. not real mail.
Most of the 3000+ messages, however, still do not show up in Mozilla.
So I tried: ...
formail -zds <my_crappy_mbox >>reinvigorated_mbox
.. but this made the file no more readable in Mozilla than the previous try.
and ...
formail -rds <my_crappy_mbox >>reinvigorated_mbox
.. but with the same result as the former try.
Naturally I removed the generated (.msf) index files as well as terminated
the Mozilla application between the tries, in case something would get
cached otherwise.
The Mozilla application simply appears to be choking on the mbox while
building the index. The progress bar is helplessly trying to move forward,
but then falls back, then forward a bit, and then back again, until it
finally gives up. In other words, the graphical indicator at the bottom
right of the application, which is meant to indicate the progress of
building the index, never reaches its maximum.
Perhaps the mbox contains some very odd characters, maybe part of some
attachment, which causes Mozilla but not other mail clients to choke.
Perhaps it is the result of some malformatted mail circulating via zoombie
machines, Outlook and whatever, that affects Mozilla on multiple platforms.
------------------------------
Date: Sat, 16 Jun 2007 11:22:20 +0200
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: Perl script to identify corrupt mbox messages?
Message-Id: <slrnf77auc.106.hjp-usenet2@zeno.hjp.at>
On 2007-06-14 14:06, Tuxedo <tuxedo@mailinator.net> wrote:
> I'm trying to repair a gigantic mbox file that appears to have been
> corrupted in that it displays only 17 of the most recent and total 3087
> messages contained in the actual file.
>
> The mail application used is Mozilla on Windows.
[...]
> The same mbox works entirely when viewed in for example MUTT or the
> standard KDE mail client, Kmail.
Have you tried copying all messages to a new mbox file with mutt or
kmail and then reading the new mbox file with Mozilla?
hp
--
_ | Peter J. Holzer | I know I'd be respectful of a pirate
|_|_) | Sysadmin WSR | with an emu on his shoulder.
| | | hjp@hjp.at |
__/ | http://www.hjp.at/ | -- Sam in "Freefall"
------------------------------
Date: Sat, 16 Jun 2007 09:40:54 GMT
From: "Mumia W." <paduille.4061.mumia.w+nospam@earthlink.net>
Subject: Re: Perl script to identify corrupt mbox messages?
Message-Id: <GeOci.1801$ZY1.1301@newsread2.news.pas.earthlink.net>
On 06/16/2007 02:24 AM, Tuxedo wrote:
> [...]
> formail -ds <my_crappy_mbox >>reinvigorated_mbox
>
> .... this certainly made some changes, in fact, 10 or so additional messages
> appear in the Mozilla index which did not show up earlier, including a
> couple without a valid sender which are now listed by Mozilla as from
> foo@bar, but which appear to be file fragments, i.e. not real mail.
>
> Most of the 3000+ messages, however, still do not show up in Mozilla.
>
> So I tried: ...
> formail -zds <my_crappy_mbox >>reinvigorated_mbox
> ... but this made the file no more readable in Mozilla than the previous try.
>
> and ...
> formail -rds <my_crappy_mbox >>reinvigorated_mbox
> ... but with the same result as the former try.
>
> Naturally I removed the generated (.msf) index files as well as terminated
> the Mozilla application between the tries, in case something would get
> cached otherwise.
>
> The Mozilla application simply appears to be choking on the mbox while
> building the index. The progress bar is helplessly trying to move forward,
> but then falls back, then forward a bit, and then back again, until it
> finally gives up. In other words, the graphical indicator at the bottom
> right of the application, which is meant to indicate the progress of
> building the index, never reaches its maximum.
>
> Perhaps the mbox contains some very odd characters, maybe part of some
> attachment, which causes Mozilla but not other mail clients to choke.
> Perhaps it is the result of some malformatted mail circulating via zoombie
> machines, Outlook and whatever, that affects Mozilla on multiple platforms.
>
Research the problem with the help of this website:
http://kb.mozillazine.org/
In particular, this article may (or may not) be of help:
http://kb.mozillazine.org/Inbox_stays_blank
Here is a script that, might improve things a little bit:
use strict;
use warnings;
require FileHandle;
require Email::Folder;
require Date::Parse;
require POSIX;
Date::Parse->import('str2time');
POSIX->import('ctime');
my $file = glob('~/tmp/mozmail/OldTests');
my $outfile = 'output.mbox';
my $fh = FileHandle->new($outfile, '>') or die("Stop: $!");
my $folder = Email::Folder->new($file);
my $count = 0;
while (my $msg = $folder->next_message) {
my $date = $msg->header('Date');
$date = ctime(str2time($date)); chomp $date;
$fh->print("From - $date\n");
$fh->print($msg->as_string() . "\n");
$count++;
}
print "There are $count messages in the folder.\n";
$fh->close;
Email::Folder and Date::Parse are modules you can download from CPAN.
The other modules are standard parts of Perl. You should change $file
and $outfile as appropriate. You shouldn't modify the original mailbox file.
Probably, you'll not need the script. Things should improve after you've
deleted the .msf (index) file and closed an reopened Mozilla.
(Followups set to alt.fan.mozilla)
------------------------------
Date: Sat, 16 Jun 2007 11:57:56 +0200
From: Tuxedo <tuxedo@mailinator.net>
Subject: Re: Perl script to identify corrupt mbox messages?
Message-Id: <f50c74$mmt$02$1@news.t-online.com>
Peter J. Holzer wrote:
> On 2007-06-14 14:06, Tuxedo <tuxedo@mailinator.net> wrote:
> > I'm trying to repair a gigantic mbox file that appears to have been
> > corrupted in that it displays only 17 of the most recent and total 3087
> > messages contained in the actual file.
> >
> > The mail application used is Mozilla on Windows.
> [...]
> > The same mbox works entirely when viewed in for example MUTT or the
> > standard KDE mail client, Kmail.
>
> Have you tried copying all messages to a new mbox file with mutt or
> kmail and then reading the new mbox file with Mozilla?
Yes that was the first thing I tried, but it didn't work :-(
I assume therefore that that some crummy characters are contained within
one or more messages, or/and in headers, which somehow cause the Mozilla to
choke, and so whatever conversion is done is simply carried forward.
The file, coming from Windows appeared to have been in DOS format. I've
un-DOS'ed it, awk-splitted each individual message, re-combed with the
proper empty line, followed by a ^From occurance, but without luck.
The file is around 150 MB and I wish I could post the entire mbox here, but
its not mine to distribute, and it surely contains much private
communication. Maybe there is a way to encode the entire content into
Mozilla safe characters as this is obviously a Mozilla bug.
------------------------------
Date: Fri, 15 Jun 2007 18:31:47 -0500
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: perl vs C for CGI
Message-Id: <slrnf768b3.mbs.tadmc@tadmc30.sbcglobal.net>
Peter J. Holzer <hjp-usenet2@hjp.at> wrote:
> On 2007-06-14 17:11, Michele Dondi <bik.mido@tiscalinet.it> wrote:
>> On Wed, 13 Jun 2007 14:35:50 +0200, "Peter J. Holzer"
>><hjp-usenet2@hjp.at> wrote:
>>>If you don't convert the *script* (as opposed to print statements within
>>>the script), apache probably can't even start the script because the
>>>linux kernel will try to invoke "/usr/bin/perl\r" which doesn't exist.
>>
>> BTW: I've always wondered... how 'bout HERE docs? Are they portable
>> across platforms or is the line ending deemed to be that of the
>> script.
>
> To my surprise they are portable at least between Unix and Windows. Perl
> seems to automatically detect the line endings and convert them to
> \x{0A} at compile time. A string written as a here document always
> contains simple "\n" characters as line endings regardless of whether
> the source file contained CRLFs or LF and whether it's executed on
> Windows or Unix.
See the "PERLIO" section in perlrun.pod:
On Win32 the default in this release is "unix crlf". Win32's "stdio"
has a number of bugs/mis-features for perl IO which are somewhat
C compiler vendor/version dependent. Using our own C<crlf> layer as
the buffer avoids those issues and makes things more uniform.
The C<crlf> layer provides CRLF to/from "\n" conversion as well as
buffering.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Fri, 15 Jun 2007 18:27:48 -0400
From: Minimiscience <minimiscience+usenet@gmail.com>
Subject: Re: question about sorting syntax
Message-Id: <yumdnc_lopH7j-7bnZ2dnUVZ_gidnZ2d@comcast.com>
Paul Lalli wrote:
> This string is then sorted amongst all the other likewise conversions
> of the strings in @words, and then the first four bytes - the
> "\0\0\0\3" part is returned into @sorted.
Actually, everything after the first four bytes ("End of the line") is returned
by the substr().
-- MiSc
------------------------------
Date: Fri, 15 Jun 2007 22:36:16 -0000
From: Paul Lalli <mritty@gmail.com>
Subject: Re: question about sorting syntax
Message-Id: <1181946976.494530.324760@n2g2000hse.googlegroups.com>
On Jun 15, 6:27 pm, Minimiscience <minimiscience+use...@gmail.com>
wrote:
> Paul Lalli wrote:
> > This string is then sorted amongst all the other likewise
> > conversions
> > of the strings in @words, and then the first four bytes - the
> > "\0\0\0\3" part is returned into @sorted.
>
> Actually, everything after the first four bytes ("End of the
> line") is returned by the substr().
Ah, yes, you're correct. That makes much more sense, but it's still a
very odd method of (presumably) sorting strings by the number of E's
they have...
Thanks for the correction,
Paul Lalli
------------------------------
Date: Fri, 15 Jun 2007 17:30:22 -0700
From: Jim Gibson <jgibson@mail.arc.nasa.gov>
Subject: Re: question about sorting syntax
Message-Id: <150620071730221002%jgibson@mail.arc.nasa.gov>
In article <1181946976.494530.324760@n2g2000hse.googlegroups.com>, Paul
Lalli <mritty@gmail.com> wrote:
> On Jun 15, 6:27 pm, Minimiscience <minimiscience+use...@gmail.com>
> wrote:
> > Paul Lalli wrote:
> > > This string is then sorted amongst all the other likewise
> > > conversions
> > > of the strings in @words, and then the first four bytes - the
> > > "\0\0\0\3" part is returned into @sorted.
> >
> > Actually, everything after the first four bytes ("End of the
> > line") is returned by the substr().
>
> Ah, yes, you're correct. That makes much more sense, but it's still a
> very odd method of (presumably) sorting strings by the number of E's
> they have...
How would you do that? Perhaps the author was dealing with a large
number of words and was trying to save memory. Here is a possibly more
normal way (untested however):
my @sorted=map { $_->[1] }
sort { $a->[0] <=> $b->[0] }
map { [ tr/eE/eE/, $_ ] } @words;
... but that takes 3 scalars and an array per word instead of just one
scalar.
Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com
------------------------------
Date: Sat, 16 Jun 2007 09:02:16 -0000
From: r3gis <regis44@gmail.com>
Subject: Re: simple regex
Message-Id: <1181984536.607464.305790@o61g2000hsh.googlegroups.com>
I did not realize that the capturing parentheses can be nested in
another one independently of the whole regex.
Thanks for help. Everything is working right now as it should :]
------------------------------
Date: Fri, 15 Jun 2007 17:28:48 -0500
From: "J. Gleixner" <glex_no-spam@qwest-spam-no.invalid>
Subject: Re: Template
Message-Id: <467312a0$0$495$815e3792@news.qwest.net>
kwan wrote:
> On Jun 15, 4:56 pm, kra...@visto.com wrote:
>> On Jun 15, 3:35 pm, kwan <kwan.ji...@gmail.com> wrote:
>>
>>> I used Mason for the template for my webserver, I have a very basic
>>> knowledge for the Mason. Do everyone who have experience in template
>>> for dynamic and complicated web site.
>>> thank you
>> What do you want?
>> What are you asking?
>
> You dont understand english?
Not your version of English. Upgrade and reinstall.
If you're looking for help with HTML::Mason, then try the masonhq.com
Web site.
------------------------------
Date: Fri, 15 Jun 2007 18:33:47 -0500
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: Template
Message-Id: <slrnf768er.mbs.tadmc@tadmc30.sbcglobal.net>
kwan <kwan.jingx@gmail.com> wrote:
> On Jun 15, 4:56 pm, kra...@visto.com wrote:
>> On Jun 15, 3:35 pm, kwan <kwan.ji...@gmail.com> wrote:
>>
>> > I used Mason for the template for my webserver, I have a very basic
>> > knowledge for the Mason. Do everyone who have experience in template
>> > for dynamic and complicated web site.
>>
>> > thank you
>>
>> What do you want?
>> What are you asking?
>
> You dont understand english?
Questions end with a question mark.
You did not ask a question.
Did you mean to ask a question?
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Sat, 16 Jun 2007 02:45:46 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: Template
Message-Id: <f4vitl.1ec.1@news.isolution.nl>
kwan schreef:
> I used Mason for the template for my webserver, I have a very basic
> knowledge for the Mason. Do everyone who have experience in template
> for dynamic and complicated web site.
You are not stating your question or problem. Please read the Posting
Guidelines, that are in a message that is posted here twice a week.
They contain also good links like
http://www.catb.org/~esr/faqs/smart-questions.html which is an article
that you really should read.
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
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 V11 Issue 522
**************************************
