Hi! This is the ezmlm program. I'm managing the
perl5-porters perl.org mailing list.
I'm working for my owner, who can be reached
at perl5-porters-ownerperl.org.
Messages to you from the perl5-porters mailing list seem to
have been bouncing. I've attached a copy of the first
bounce
message I received.
If this message bounces too, I will send you a probe. If the
probe bounces,
I will remove your address from the perl5-porters mailing
list,
without further notice.
I've kept a list of which messages from the perl5-porters
mailing list have
bounced from your address.
Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per
request),
send an empty message to:
<perl5-porters-get.123_145perl.org>
To receive a subject and author list for the last 100 or so
messages,
send an empty message to:
<perl5-porters-indexperl.org>
Here are the message numbers:
123451
123452
123453
123454
123455
123456
123457
123458
123459
123460
123461
123462
123463
123464
123465
123466
123467
123468
123469
123470
123471
123472
123473
123474
123475
123476
123477
123478
123479
123480
123481
123482
123483
123484
123485
123486
123487
123488
123489
123490
123491
123492
123493
123494
123495
123496
123497
123498
123499
123500
123501
123502
123503
123504
123505
123506
123507
123508
123509
123510
123511
123512
123513
123514
123515
123516
123517
123518
123519
123520
123521
123522
123523
123524
123525
123526
123527
123528
123529
123530
123531
123532
123533
123534
123535
123536
123537
123538
123539
123540
123541
123542
123543
123544
123545
123546
123547
123548
123549
123550
123551
123552
123553
123554
123555
123556
123557
123558
123559
123560
123561
123562
123563
123564
123565
123566
123567
123568
123569
123570
123571
123572
123573
123574
123575
123576
123577
123578
123579
123580
123582
123581
123583
123584
123585
123586
123587
123588
123589
123590
123591
123592
123593
123594
123595
123596
123597
123598
123599
123600
123601
123602
123603
123604
123605
123606
123607
123608
123609
123610
123611
123612
123613
123614
123615
123616
123617
123618
123619
123620
123621
123622
123623
123624
123625
123626
123627
123628
123629
123630
123631
123632
123633
123634
123635
123636
123637
123638
123639
123640
123641
123642
123643
123644
123645
123646
123647
123648
123649
123650
123651
123652
123653
123655
123654
123656
123657
123658
123659
123660
123771
123772
123773
123774
123775
123776
123777
123778
123779
123780
123781
123783
123782
123784
123785
123786
123787
123788
123790
123789
123792
123791
123793
123794
123795
123796
123797
123798
123799
123800
123801
123802
123803
123804
123805
123806
123807
123808
123809
123810
123811
123812
123813
123814
123815
123816
123817
123818
123819
123820
123821
123822
123823
123824
123825
123826
123827
123828
123829
123830
123831
123832
123833
123834
123835
123836
123837
123838
123839
123840
123841
123842
123843
123844
123845
123846
123847
123848
123849
123850
123851
123852
123853
123854
123855
123856
123857
123858
123859
123860
123861
123862
123863
123864
123865
123866
123867
123868
123869
123870
123871
123872
123873
123874
123875
123876
123877
123878
123879
123880
123881
123882
123883
123884
123885
123886
123887
123888
123889
123890
123891
123892
--- Enclosed is a copy of the bounce message I received.
Return-Path: <>
Received: (qmail 30728 invoked from network); 19 Apr 2007
11:29:58 -0000
Received: from x1a.develooper.com (HELO x1.develooper.com)
(216.52.237.111)
by lists.develooper.com with SMTP; 19 Apr 2007 11:29:58
-0000
Received: (qmail 2812 invoked by uid 225); 19 Apr 2007
11:29:58 -0000
Delivered-To: perl5-porters-return-123451-bond=yahoo.comperl.org
Received: (qmail 2772 invoked by alias); 19 Apr 2007
11:29:55 -0000
X-Spam-Status: No, hits=4.9 required=8.0
tests=BAYES_00,DK_POLICY_SIGNSOME,RAZOR2_CF_RANGE_51_100,RA
ZOR2_CF_RANGE_E4_51_100,RAZOR2_CHECK,SPF_HELO_PASS
X-Spam-Check-By: la.mx.develooper.com
Received: from starfire.yahoo.com (HELO starfire.yahoo.com)
(66.98.192.98)
by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Thu,
19 Apr 2007 04:29:52 -0700
Received: by starfire.yahoo.com (Postfix)
id 61037208094; Thu, 19 Apr 2007 06:29:50 -0500 (CDT)
Date: Thu, 19 Apr 2007 06:29:50 -0500 (CDT)
From: MAILER-DAEMONyahoo.com (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: perl5-porters-return-123451-bond=yahoo.comperl.org
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report;
report-type=delivery-status;
boundary="2A897208097.1176982190/starfire.yahoo.com&qu
ot;
Content-Transfer-Encoding: 8bit
Message-Id: <20070419112950.61037208094starfire.yahoo.com>
X-Virus-Checked: Checked
This is a MIME-encapsulated message.
--2A897208097.1176982190/starfire.yahoo.com
Content-Description: Notification
Content-Type: text/plain; charset=us-ascii
This is the mail system at host starfire.yahoo.com.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached
below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<bondyahoo.com>: cannot update mailbox /var/mail/bond
for user bond. error
writing message: File too large
--2A897208097.1176982190/starfire.yahoo.com
Content-Description: Delivery report
Content-Type: message/delivery-status
Reporting-MTA: dns; starfire.yahoo.com
X-Postfix-Queue-ID: 2A897208097
X-Postfix-Sender: rfc822;
perl5-porters-return-123451-bond=yahoo.comperl.org
Arrival-Date: Thu, 19 Apr 2007 06:29:50 -0500 (CDT)
Final-Recipient: rfc822; bondyahoo.com
Original-Recipient: rfc822;bondyahoo.com
Action: failed
Status: 5.2.2
Diagnostic-Code: x-unix; input/output error
--2A897208097.1176982190/starfire.yahoo.com
Content-Description: Undelivered Message
Content-Type: message/rfc822
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: amavisd-new at yahoo.com
Received: from starfire.yahoo.com ([127.0.0.1])
by localhost (starfire.yahoo.com [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id hrt47RH8sRFq for <bondyahoo.com>;
Thu, 19 Apr 2007 06:29:43 -0500 (CDT)
Received: from lists.develooper.com (x6.develooper.com
[63.251.223.186])
by starfire.yahoo.com (Postfix) with SMTP id 76C7C208094
for <bondyahoo.com>; Thu, 19 Apr 2007 06:29:42
-0500 (CDT)
Received: (qmail 30215 invoked by uid 514); 19 Apr 2007
11:29:37 -0000
Mailing-List: contact perl5-porters-helpperl.org;
run by ezmlm
Precedence: bulk
list-help: <mailto:perl5-porters-helpperl.org>
list-unsubscribe: <mailto:perl5-porters-unsubscribeperl.org>
list-post: <mailto:perl5-portersperl.org>
X-List-Archive: <http://nntp.perl.org/group/perl.perl5.porters/123451>
List-Id: <perl5-porters.perl.org>
Delivered-To: mailing list perl5-portersperl.org
Received: (qmail 30203 invoked from network); 19 Apr 2007
11:29:37 -0000
Delivered-To: perl5-portersperl.org
X-Spam-Check-By: la.mx.develooper.com
Received-SPF: pass (x1.develooper.com: domain of gerardtty.nl
designates 85.17.53.114 as permitted sender)
Date: Thu, 19 Apr 2007 13:33:21 +0200
From: Gerard Goossen <gerardtty.nl>
To: Rafael Garcia-Suarez <rgarciasuarezgmail.com>
Cc: perl5-portersperl.org
Subject: Re: [PATCH] madprop about forced words
Message-ID: <20070419113321.GE19244ostwald>
References: <20070329161042.GG20231ostwald>
<b77c1dce0704060625p6e62cd23p7da1338af109c02bmail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="xesSdrSSBC0PokLI"
Content-Disposition: inline
In-Reply-To:
<b77c1dce0704060625p6e62cd23p7da1338af109c02bmail.gmail.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Old-Spam-Status: No, hits=0.0 required=4.0
tests=AWL: 0.247,BAYES_00: -1.665
--xesSdrSSBC0PokLI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Apr 06, 2007 at 03:25:24PM +0200, Rafael
Garcia-Suarez wrote:
> On 29/03/07, Gerard Goossen <gerardtty.nl> wrote:
> >Patch add a new madprop 'B' saying that something
was forced to be a
> >word. (Very useful when converting barewords).
>
> Thanks, applied as #30850.
> I notice a list of MAD keys at the end of op.h. 'B' is
listed there,
> used in op.c (line 5455 currently). I don't claim to
understand
> everything, but maybe this implies that the doc should
be updated,
> and/or another letter be chosen for forced words ?
This patch changes the madprop to 'g' and add it to the doc
(Sorry for
being slow...)
I didn't know that they were listed in op.h, and the 'B's
probably would
not conflict, but for safety I changed it madprop to 'g'
(the first free
lower case letter I could find).
We are running a bit out of letter so I was planning to
refactor the
madprop to use strings instead of letters (i.e. change
<char mad_key> to <const char* mad_key> and
<curmad('X', ...)>
to <cumad("random", ...)>, any objections?
--xesSdrSSBC0PokLI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=madpropB2g
commit bd6c6654f5d345a81bc3a1176c34f32c2d043470
Author: gerard <gerardtty.nl>
Date: Thu Apr 19 13:06:05 2007 +0200
Change madprop for forced words to 'g' instead of 'B'.
Change madprop for forced words to 'g' instead of 'B'
because it was
already used and add doc about the madprop.
diff --git a/op.h b/op.h
index d9d5336..b6c45ef 100644
--- a/op.h
+++ b/op.h
-696,6
+696,7 struct token {
* E tr/E/R/, /E/
* f folded constant op
* F peg op for format
+ * g op was forced to be a word
* i if/unless modifier
* I if/elsif/unless statement
* K retired kid op
diff --git a/toke.c b/toke.c
index 0485df1..d5fbd0a 100644
--- a/toke.c
+++ b/toke.c
-1365,7
+1365,7 S_force_word(pTHX_ register char *start, int token,
int check_keyword, int allow
}
}
if (PL_madskills)
- curmad('B', newSVpvs( "forced" ));
+ curmad('g', newSVpvs( "forced" ));
NEXTVAL_NEXTTOKE.opval
= (OP*)newSVOP(OP_CONST,0,
S_newSV_maybe_utf8(aTHX_ PL_tokenbuf, len));
--xesSdrSSBC0PokLI--
--2A897208097.1176982190/starfire.yahoo.com--
|