On 9/24/05, Nicholas Clark [EMAIL PROTECTED] wrote:
The distribution contains a shell script mv-if-diff, which does what it says.
The Makefile uses it to avoid touching the timestamps on automatically
generated files, if they've not actually changed. For example, lib/Config.pm
I notice that
On 9/1/05, Nicholas Clark [EMAIL PROTECTED] wrote:
One of the good ideas of the Google Summer of Code was to insist that every
project has a mentor; an experienced person to advise and guide the grantee.
I'm wondering whether we could embrace this idea for perl5-porters. We often
feel rather
On 8/31/05, via RT Thilo Girmann [EMAIL PROTECTED] wrote:
# New Ticket Created by Thilo Girmann
# Please include the string: [perl #37038]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=37038
This is a bug
On 15 Aug 2005 21:05:22 -0700, Gisle Aas [EMAIL PROTECTED] wrote:
/tmp/perl-aekojpkufyzuasapckiyadszkxhdobbloqazueglxwkksqoohxylbukriemwutaerimizyjbxfnynbotpkfurxdgmkhwefhqxhyptjatvzulotpskbfuda
Thats quite the directory name there, must be a bitch to type
yves
--
perl -Mre=debug -e
On 8/3/05, Randy W. Sims [EMAIL PROTECTED] wrote:
Piotr Fusik (via RT) wrote:
# New Ticket Created by Piotr Fusik
# Please include the string: [perl #36766]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=36766
On 8/5/05, Tim Jenness [EMAIL PROTECTED] wrote:
Do you want to patch File::Temp to make this work properly on Win32 (I
don't know the API so never implemented something like that). If I recall
correctly Pod::Perldoc started off using File::Temp until problems with
win32 temp files turned up.
On 8/5/05, Konovalov, Vadim [EMAIL PROTECTED] wrote:
Do you want to patch File::Temp to make this work properly
on Win32 (I
don't know the API so never implemented something like
that). If I recall
correctly Pod::Perldoc started off using File::Temp until
problems with
win32 temp
On 8/5/05, Randy W. Sims [EMAIL PROTECTED] wrote:
demerphq wrote:
On 8/3/05, Randy W. Sims [EMAIL PROTECTED] wrote:
Piotr Fusik (via RT) wrote:
# New Ticket Created by Piotr Fusik
# Please include the string: [perl #36766]
# in the subject line of all future correspondence about
On 8/5/05, Konovalov, Vadim [EMAIL PROTECTED] wrote:
However perl *does* have proper temp files inside core,
here is an excerpt
from win32/win32.c:
DllExport int
win32_tmpfd(void)
{
dTHX;
char prefix[MAX_PATH+1];
char filename[MAX_PATH+1];
DWORD len
On 8/5/05, Konovalov, Vadim [EMAIL PROTECTED] wrote:
And perldoc invented wrong wheel :)
Well, this makes File::Temp patchable without adding modules to the
core which is a good step. :-)
As I understood with some delays, there are intentions to remove perldoc's
own logic with
On 8/3/05, Joshua Juran [EMAIL PROTECTED] wrote:
On Aug 2, 2005, at 4:18 AM, demerphq wrote:
On 7/28/05, Joe McMahon [EMAIL PROTECTED] wrote:
On Jul 28, 2005, at 12:49 AM, Piotr Fusik wrote:
Note that a block by itself is semantically identical to a loop
-that executes once. Thus
On 7/28/05, Joe McMahon [EMAIL PROTECTED] wrote:
On Jul 28, 2005, at 12:49 AM, Piotr Fusik wrote:
Note that a block by itself is semantically identical to a loop
-that executes once. Thus Clast can be used to effect an early
+that executes once. Thus Clast can be used to affect an
On 7/14/05, Johan Vromans [EMAIL PROTECTED] wrote:
Rick Delaney [EMAIL PROTECTED] writes:
use strict;
package Foo::Bar;
our @ISA = qw(Foo);
package Foo::Baz;
our @ISA = qw(Foo);
This is where we have use base for.
use base sucks. It uses horrible heuristics
On 7/9/05, Ken Williams [EMAIL PROTECTED] wrote:
On Jul 8, 2005, at 4:50 PM, yves orton via RT wrote:
Sorry, i guess I didnt express myself properly. You cant clean up a
relative path properly without knowing where it is relative to.
Consider the following path:
..\..\foo
If
On 7/9/05, Michael G Schwern [EMAIL PROTECTED] wrote:
I'm not wedded to the name, but attached is a proof-of-concept of a routine
which collapses updirs. This is a solution to the problem whether or not
canonpath() should collapse them. Let the user decide.
0 ~$ perl -w ~/tmp/foo.plx
On 7/9/05, Glenn Linderman [EMAIL PROTECTED] wrote:
On approximately 7/8/2005 2:07 PM, came the following characters from
the keyboard of demerphq:
On 7/8/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Fri, Jul 08, 2005 at 03:50:49PM +0200, demerphq wrote:
Im not sure
On 7/8/05, Dave Mitchell [EMAIL PROTECTED] wrote:
On Tue, Jun 07, 2005 at 04:28:08PM -, Nicholas Clark wrote:
./perl -Ilib -we '$term = \xe9; $target = \xe9\x{100}; chop $target;
$target =~ /$term/i'
Malformed UTF-8 character (unexpected non-continuation byte 0x00,
immediately after
On 7/8/05, Dave Mitchell [EMAIL PROTECTED] wrote:
On Fri, Jul 08, 2005 at 09:24:42AM +0200, demerphq wrote:
it turns out perl is totally borked for
$utf8 =~ /latin1/i
and
$latin1 =~ /$utf8/i
unless all the chars happen to be 0x7f.
The case where the pattern
On 7/6/05, Ken Williams [EMAIL PROTECTED] wrote:
On Jul 6, 2005, at 4:00 PM, Dinger, Tom wrote:
To be perfectly honest, I don't care which way it is fixed, as long
as the
result still points to the right file.
Of course. That's what I'm asking: is bar guaranteed on Windows to
be
On 7/8/05, Dave Mitchell [EMAIL PROTECTED] wrote:
On Fri, Jul 08, 2005 at 09:24:42AM +0200, demerphq wrote:
it turns out perl is totally borked for
$utf8 =~ /latin1/i
and
$latin1 =~ /$utf8/i
unless all the chars happen to be 0x7f.
The case where the pattern
On 7/8/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Fri, Jul 08, 2005 at 03:50:49PM +0200, demerphq wrote:
Im not sure if this is useful, but many of the things that File::Spec
tries to do on win32 are actually supported directly by the Win32 API.
IMO at least some of File::Spec's
On 7/8/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Fri, Jul 08, 2005 at 11:07:22PM +0200, demerphq wrote:
should be testing here, but i beleive the problem you are thinking of
is due to symlinks to a directory? If so then the win32 equivelent
would be a junction I think
On 7/8/05, Glenn Linderman [EMAIL PROTECTED] wrote:
On approximately 7/8/2005 1:53 PM, came the following characters from
the keyboard of Michael G Schwern:
On Fri, Jul 08, 2005 at 03:50:49PM +0200, demerphq wrote:
Im not sure if this is useful, but many of the things that File::Spec
On 6/30/05, Michael G Schwern [EMAIL PROTECTED] wrote:
Could have sworn I attached the tests.
Which time? :-)
--
perl -Mre=debug -e /just|another|perl|hacker/
On 6/30/05, David Dyck [EMAIL PROTECTED] wrote:
The following 3 line test program results in the same error when pushing
__PACKAGE__
onto @ISA:
our @ISA = qw(a b);
push @ISA, 'main';
push @ISA, __PACKAGE__;
Modification of a read-only value attempted at isabug.pl line 3.
On 6/29/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Tue, Jun 28, 2005 at 06:25:31PM -, Justin Mason wrote:
However, there is one key difference: while ($io) and while
($io-getline) ha ve different behaviour.If the last line of an input
file
contains 0 (with no trailing
On 6/21/05, Rafael Garcia-Suarez [EMAIL PROTECTED] wrote:
I added Archive::Tar to the core, this being the last addition before
CPANPLUS.
A::T doesnt seem too happy on Win32:
Failed Test Stat Wstat Total Fail Failed List of Failed
On 6/20/05, Steve Hay [EMAIL PROTECTED] wrote:
Nicholas Clark wrote:
(snip error result)
I suspect that this may be me and it may be change 24896.
I suspect not. I think it is the same old intermittent failure that
I've been having for a lng time now, e.g. the smokes at patchlevels
On 6/17/05, Steve Hay [EMAIL PROTECTED] wrote:
Jan Dubois wrote:
On Thu, 16 Jun 2005, Steve Hay wrote:
Well, I'm really confused now.
A simple test program shows that system(copy ...) does indeed work
fine, even with tainting on and $ENV{PATH} cleared (as per op/taint.t).
On 6/17/05, demerphq [EMAIL PROTECTED] wrote:
print Copying '$exe' to .\n;
system(copy $exe .) die Error: $!;
Sigh. I guess $exe should be quoted. Although maybe not. I hate the
inconsistancies in argument parsing in cmd.exe.
system(qq[copy $exe .]) die Error: $!;
--
perl -Mre=debug -e
On 6/17/05, Steve Hay [EMAIL PROTECTED] wrote:
Ah, but I see you're using ActivePerl 811 (and I dare say Jan is too ;-)
I'm using a Perl that I built myself. If I try your program with AP811
then I get the same error that you see. Also, when testing t/op/taint.
I was running a different
On 6/16/05, Mark Jason Dominus [EMAIL PROTECTED] wrote:
yves:
Using UNIVERSAL::isa() is IMO bad as its suseptible to
my $obj=3Dbless [],'HASH';
type nonsense.
Perhaps, but it seems to me that someone doing that is doing it
deliberately to try to deceive the UNIVERSAL::isa
On 6/16/05, Nicholas Clark [EMAIL PROTECTED] wrote:
Sorry for the delay in this answer
No problem.
On Wed, Jun 01, 2005 at 06:54:30PM +0200, demerphq wrote:
On 6/1/05, Nicholas Clark [EMAIL PROTECTED] wrote:
It would be interesting if someone found some good way of benchmarking
perl
Should this be perlbug'ed? It seems like the + operator is mistakenly
being taken for the unary plus and not the binary plus.
perl -Mwarnings -e my $x = 10; my $y = 20; print $x +$y;
print() on unopened filehandle 10 at -e line 1.
--
perl -Mre=debug -e /just|another|perl|hacker/
On 6/15/05, H.Merijn Brand [EMAIL PROTECTED] wrote:
On Wed, 15 Jun 2005 00:59:55 -0700, Michael G Schwern [EMAIL PROTECTED]
wrote:
On Wed, Jun 15, 2005 at 08:51:43AM +0200, demerphq wrote:
Should this be perlbug'ed? It seems like the + operator is mistakenly
being taken for the unary
On 6/15/05, Rafael Garcia-Suarez [EMAIL PROTECTED] wrote:
demerphq wrote:
Although there is odd behaviour of
'/' but i suspect that is something totally different. Also note that
adding parens doesn't help.
/ is the beggining of a /.../ regexp. Note that // still parses as a
binary
On 6/15/05, Tassilo von Parseval [EMAIL PROTECTED] wrote:
so it's not that the current behaviour should be such a surprise to an
experienced user. For me it's mostly an aesthetic question really. Do we
want this couple:
print $x +$y; # means: $x + $y
print { $x } +$y;
or
On 6/15/05, Tassilo von Parseval [EMAIL PROTECTED] wrote:
On Wed, Jun 15, 2005 at 01:30:12PM +0200 demerphq wrote:
On 6/15/05, Tassilo von Parseval [EMAIL PROTECTED] wrote:
so it's not that the current behaviour should be such a surprise to an
experienced user. For me it's mostly
On 6/15/05, Rafael Garcia-Suarez [EMAIL PROTECTED] wrote:
demerphq wrote:
If we are going to accept this bug then we need specifically document
it as it totally breaks reasonable expectation. And the inconsistancy
in it is IMO a big problem. Why should a space determine whether
On 6/14/05, Steve Hay [EMAIL PROTECTED] wrote:
demerphq wrote:
Ok, fine. So we cant go that route. Howsabout a different mechansim.
We can replace the usage of XCOPY with a batchfile that acts as a
wrapper to OSize the command, ie here is xcopyit.bat that i just put
together:
[snip batch
On 6/15/05, Mark Jason Dominus [EMAIL PROTECTED] wrote:
The attached patch rephrases three pieces of Perl documentation which
suggest that calling UNIVERSAL::isa() or UNIVERSAL::can() directly is a
good idea. The revised version explains why it's a bad idea and gives
more correct
On 6/13/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Sun, Jun 12, 2005 at 11:42:01AM +0200, Tels wrote:
Semi-stupid question. How do I get different patch-levels from blead? I
know how to get the latest, but have no idea how to checkout a certain
patch number, or even how to find out
On 6/13/05, vadim [EMAIL PROTECTED] wrote:
Probably better this way:
--- perl/win32/Makefile.orig2005-06-12 03:22:35.0 -0700
+++ perl/win32/Makefile 2005-06-12 12:42:16.12936 -0700
@@ -696,7 +696,7 @@
!ENDIF
# specify static extensions here
On 6/13/05, vadim [EMAIL PROTECTED] wrote:
Change 24806 by [EMAIL PROTECTED] on 2005/06/12 09:54:07
Subject: improve static build for win32/Makefile
From: vadim [EMAIL PROTECTED]
Date: Sun, 12 Jun 2005 14:09:11 -0400
Message-Id: [EMAIL PROTECTED]
I guess it
I think something applied today (in the past hour or so) broke threads.xs
I rsynched this morning and there was no problem, i re-rsynched an
hour or so later and boom.
Yves
Making threads
nmake -nologo
cl -c-nologo -Gf -W3 -MD -Zi -DNDEBUG -O1 -DWIN32
-D_CONSOLE -DNO_STRICT
On 6/13/05, demerphq [EMAIL PROTECTED] wrote:
On 6/13/05, vadim [EMAIL PROTECTED] wrote:
Change 24806 by [EMAIL PROTECTED] on 2005/06/12 09:54:07
Subject: improve static build for win32/Makefile
From: vadim [EMAIL PROTECTED]
Date: Sun, 12 Jun 2005 14:09:11 -0400
On 6/13/05, H.Merijn Brand [EMAIL PROTECTED] wrote:
On Mon, 13 Jun 2005 15:41:41 -0400, vadim [EMAIL PROTECTED] wrote:
I already have a patch.
May be its not perfect.
I'll leave it to Steve
Please could we not forget or overlook or otherwise warnock the issue
of the /y flag on XCOPY and
On 6/13/05, Steve Hay [EMAIL PROTECTED] wrote:
demerphq wrote:
On 6/13/05, H.Merijn Brand [EMAIL PROTECTED] wrote:
On Mon, 13 Jun 2005 15:41:41 -0400, vadim [EMAIL PROTECTED] wrote:
I already have a patch.
May be its not perfect.
I'll leave it to Steve
Please could we
On 6/12/05, Tels [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Moin,
On Sun, Jun 12, 2005 at 12:12:22AM +0200, David Landgren wrote:
Executive summary: it looks like 5.8.7 is doing a better job than blead
at the moment. I haven't looked closely at what I chose in the
On 6/10/05, Nicholas Clark [EMAIL PROTECTED] wrote:
I believe that $1 etc are stored as byte offsets into
this (copied) string.
This is correct. The OPEN/CLOSE handlers in regexec.c regmatch()
update the values of the @- and @+ arrays.
Yves
--
perl -Mre=debug -e /just|another|perl|hacker/
Hi,
Ive been trying to help Ken get the latest version of Pathtools
(Cwd.xs) to work properly on Win32 5.6.x. Overall this hasnt been much
of a problem, except that for the life of me I cant get Cwd.xs to
return tainted values.
The following code is an example of an XS routine that works fine in
On 6/3/05, Ken Williams [EMAIL PROTECTED] pointed out:
If I understand the code correctly, Win32 never actually uses this
abs_path() function anyway (it uses the built-in _NT_cwd() for cwd-ish
functions and the pure-perl fast_abs_path() for abs_path-ish
functions), so the only reason to have
2. Fix this quoting style in all non-generated other pods
The generators also should no longer do this right?
yves
--
perl -Mre=debug -e /just|another|perl|hacker/
If you answered yes like I did then youre in for a surprise.
I got bitten by this today and before I perlbug it I just want to
check if anybody thinks the differing behaviour of $fh and $fh
is correct (first has no spaces inside the angle brackets second has
them before and after the $fh). It
On 6/1/05, Nicholas Clark [EMAIL PROTECTED] wrote:
It would be interesting if someone found some good way of benchmarking perl,
and compared current blead with released 5.9.2
Is perlbench not the right way? What does good imply for you?
Also shouldn't Devel::Size count the memory allocated to
On 5/31/05, Rafael Garcia-Suarez [EMAIL PROTECTED] wrote:
Andy Lester wrote:
- SvCUR_set (data-datasv, 0);
}
+ SvCUR_set(data-datasv, len);
This seems suspicious to me.
Look at the logic:
if (len) {
memmove (start, start + data-next_out, len + 1);
-
On 31 May 2005 14:11:03 -, via RT Nicholas Clark
[EMAIL PROTECTED] wrote:
# New Ticket Created by Nicholas Clark
# Please include the string: [perl #36050]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=36050
On 5/31/05, Nicholas Clark [EMAIL PROTECTED] wrote:
On Tue, May 31, 2005 at 04:20:40PM +0200, demerphq wrote:
On 31 May 2005 14:11:03 -, via RT Nicholas Clark
[EMAIL PROTECTED] wrote:
# New Ticket Created by Nicholas Clark
# Please include the string: [perl #36050
On 5/31/05, David Nicol [EMAIL PROTECTED] wrote:
and that doc text from perlre (5.8.6) has a grammar bug in it as well
(put 'it' after 'makes').
YS Yes.
it shows how few people have actually read that note. :)
uri
I actually thought it was by design that way, as part of
The following two lines cause a segfault:
$str = { . (0x00, x 25600) . 0x00};
$str =~ /^(0|0x00+|\{(0x00,\s*)*0x00\})$/;
Here is the debug output of a reduced version of this (x 2 in the code
above). If you remove the \s* and use a space instead the problem goes
away. From the output of
On 26 May 2005 08:13:03 -, via RT fdhsbgeryft lkjhuibfmfsi
[EMAIL PROTECTED] wrote:
# New Ticket Created by fdhsbgeryft lkjhuibfmfsi
# Please include the string: [perl #35982]
# in the subject line of all future correspondence about this issue.
# URL:
On 5/26/05, demerphq [EMAIL PROTECTED] wrote:
On 26 May 2005 08:13:03 -, via RT fdhsbgeryft lkjhuibfmfsi
[EMAIL PROTECTED] wrote:
...
I hope I have been specific enough for you to identify
this bug with relative ease, I have never submitted a
bug before and I'm not exactly
On 5/26/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Thu, May 26, 2005 at 02:59:04PM +0200, demerphq wrote:
Try www.perlmonks.org next time you suspect you've found a bug. The
folks there can help you sort out if its a bug in your code or in the
core. :-) Plus they generally speaking
On 5/26/05, Yitzchak Scott-Thoennes [EMAIL PROTECTED] wrote:
On Thu, May 26, 2005 at 10:39:48PM +0200, demerphq wrote:
On 5/26/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Thu, May 26, 2005 at 02:59:04PM +0200, demerphq wrote:
Try www.perlmonks.org next time you suspect you've found
On 5/26/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Thu, May 26, 2005 at 10:39:48PM +0200, demerphq wrote:
On 5/26/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Thu, May 26, 2005 at 02:59:04PM +0200, demerphq wrote:
PM might do better for perl bugs than module bugs since, you're
On Sat, 21 May 2005 22:22 +0100, Steve Hay [EMAIL PROTECTED] wrote:
Automated smoke report for 5.9.3 patch 24533
TANGAROA.uk.radan.com: Intel(R) Pentium(R) 4 CPU 2.00GHz(~1992 MHz) (x86/1
cpu)
onMSWin32 - WinXP/.Net SP1
using ? unknown cc version
smoketime 2 minutes
* unicore text files. I thought the tables were generated via
mktables upon build time, are the txt files really needed? They
weight about 5.6 Mb, compare this to 28 Mb for the entire perl586 lib
dir...
They're used by the core...
So mktables generates some tables, but the initial
On 5/19/05, Abhijit Menon-Sen [EMAIL PROTECTED] wrote:
At 2005-05-18 08:30:44 -, [EMAIL PROTECTED] wrote:
The following program demonstrates that with one module using
warnings::register the output is as expected, with two modules
using it the output changes to be an ugly assignment
On 5/22/05, Tels [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Moin,
attached is a patch that should improve the aligning of struct members in
RExC_state_t (assuming that 4 chars are as big as the other memebers,
which is true for x86 and 32 bit).
Some of the flags like
On 5/20/05, Nicholas Clark [EMAIL PROTECTED] wrote:
I think I've come to the end of experimenting with making core data
structures smaller. Frustratingly, while I can do 3 different things that
all seem to make SpamAssassin's tests 1% faster, if I put all 3 together
they don't add up, which
On 5/20/05, Rafael Garcia-Suarez [EMAIL PROTECTED] wrote:
Yitzchak Scott-Thoennes wrote:
$ bleadperl -le 'print for qw(foo bar) x 2'
foo
bar
foo
bar
That's the opposite of what I was trying to say.
Yes, I'm quite aware of this :) A nonetheless is missing in my
previous
On 5/20/05, Dave Mitchell [EMAIL PROTECTED] wrote:
On Fri, May 20, 2005 at 03:36:48AM -0700, Yitzchak Scott-Thoennes wrote:
I was actually hoping these warnings would provide some incentive
for Dave to finish :)
See http://groups.google.com/[EMAIL PROTECTED]
Deary me: did I really say
On 18 May 2005 08:30:44 -, via RT yves orton
[EMAIL PROTECTED] wrote:
# New Ticket Created by yves orton
# Please include the string: [perl #35857]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=35857
This
On 5/13/05, Ronald J Kimball [EMAIL PROTECTED] wrote:
On Fri, May 13, 2005 at 12:02:22PM +0200, Daniel Pfeiffer wrote:
Hallo Rafael,
Inconsistencies of this kind are a terrible trap! For one thing the doc
states that this is not locale-dependent but a builtin. That sounds like
a lie
On 5/4/05, Steve Peters [EMAIL PROTECTED] wrote:
On Wed, May 04, 2005 at 03:28:47PM +0100, Dave Mitchell wrote:
On Wed, May 04, 2005 at 10:37:43AM -, Brendan O'Dea wrote:
Segfault in the following code:
#!/usr/bin/perl
for ($_ = 1; $_ 3; $_++)
{
AGAIN:
if
On 5/3/05, Nicholas Clark [EMAIL PROTECTED] wrote:
Is this behaviour documented anywhere?
perl -le '@c = one two three =~ /(?: (\S+))+/; print foreach @c'
three
Specifically that captures inside groupings that repeat capture the last
string.
I can't find it in perlre*.pod
No. Me
On 5/3/05, Brad Baxter [EMAIL PROTECTED] wrote:
SNIP
I mention this because of the suggestion to use -X, which is
apparently already in use.
Yes, my use of X there was not really meant to be literal but rather
as a placeholder for something nicer. But as you have pointed out (in
a much nicer
On 5/3/05, Brad Baxter [EMAIL PROTECTED] wrote:
On Tue, 3 May 2005, Abigail wrote:
On Tue, May 03, 2005 at 11:14:51AM -0400, Brad Baxter wrote:
Of these, none stands out to me as an obvious choice for the kinds of
uses that have been suggested. Would overloading -e with a single
On 5/2/05, Steven Philip Schubiger [EMAIL PROTECTED] wrote:
regcomp.c: In function `S_make_trie':
regcomp.c:905: warning: `scan' might be used uninitialized in this function
CCCMD = cc -DPERL_CORE -c -DDEBUGGING -fno-strict-aliasing -pipe
-I/usr/local/include -O2 -Wall
Steven
On 4/29/05, Ronald J Kimball [EMAIL PROTECTED] wrote:
On Fri, Apr 29, 2005 at 03:37:06PM +0200, demerphq wrote:
On 4/29/05, Ronald J Kimball [EMAIL PROTECTED] wrote:
On Fri, Apr 29, 2005 at 10:44:34AM +0200, H.Merijn Brand wrote:
Then let me reword. I'd like it to be possible
On 4/30/05, Ronald J Kimball [EMAIL PROTECTED] wrote:
On Sat, Apr 30, 2005 at 12:40:18PM +0200, demerphq wrote:
I think the -X modifier would change other aspects of the behaviour of
-e anyway. If something like the following becomes
-Xe #init -p #preprocess -e #postprocess
#init
On 4/29/05, Yitzchak Scott-Thoennes [EMAIL PROTECTED] wrote:
On Thu, Apr 28, 2005 at 03:43:24PM +0200, H.Merijn Brand wrote:
As my example shows, if the `extension' would be accepted, in whatever form,
I also suggest to define that each -e part gets it's own braces/scope
Yuck! Right now,
On 4/29/05, Ronald J Kimball [EMAIL PROTECTED] wrote:
On Fri, Apr 29, 2005 at 10:44:34AM +0200, H.Merijn Brand wrote:
Then let me reword. I'd like it to be possible.
lt09:/home/merijn 104 perl -l -e 'my $x = 42' -e 'print $x'
syntax error at -e line 2, near print
Execution of -e
Nice idea, but with complex ramifications. However, you have a point, so
I'll mark this bug as rejected.
I think the documentation already promises otherwise. perlrun says:
Personally i think this feature would be a worthy 5.10'ism. Since
apparently this means breaking old semantics maybe
On 4/25/05, Nicholas Clark [EMAIL PROTECTED] wrote:
On Sun, Apr 24, 2005 at 11:03:49PM +0300, Jarkko Hietaniemi wrote:
Nicholas, since you've integrated the UCD 4.1.0 files to maint
you should probably integrate this patch, too :-/
I have now.
Thanks Nick... Now its Raphaels turn i guess.
On 4/2/05, Nicholas Clark [EMAIL PROTECTED] wrote:
On Sat, Apr 02, 2005 at 11:31:09AM +0300, Jarkko Hietaniemi wrote:
The Unicode 4.1.0 is out: http://www.unicode.org/versions/Unicode4.1.0/
Attached is the patch to synchronize blead (missed 5.9.2, rats) with it.
P.S. Someone more
On 4/24/05, Jarkko Hietaniemi [EMAIL PROTECTED] wrote:
demerphq wrote:
On 4/2/05, Nicholas Clark [EMAIL PROTECTED] wrote:
On Sat, Apr 02, 2005 at 11:31:09AM +0300, Jarkko Hietaniemi wrote:
The Unicode 4.1.0 is out: http://www.unicode.org/versions/Unicode4.1.0/
Attached is the patch
On 4/20/05, Dave Mitchell [EMAIL PROTECTED] wrote:
I get the following output:
[EMAIL PROTECTED] Trec]$ perl -e use blah;
Unknown error
Compilation failed in require at -e line 1.
BEGIN failed--compilation aborted at -e line 1.
This has been fixed in the development version of Perl;
On 4/21/05, Dave Mitchell [EMAIL PROTECTED] wrote:
On Wed, Apr 20, 2005 at 09:05:59PM -0500, David Nicol wrote:
doesn't myprint have to be defined, or at least have a prototype
registered for it, before reaching that point, to prevent it
from getting parsed as
LOG-myprint(@_)
,
On 19 Apr 2005 22:13:24 -, via RT Dan Jacobson
[EMAIL PROTECTED] wrote:
# New Ticket Created by Dan Jacobson
# Please include the string: [perl #35045]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=35045
On 4/18/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Sun, Apr 17, 2005 at 09:37:10PM +0200, demerphq wrote:
Which assumes that things are being run from exactly two levels below the
perl source directory such as ext/Foo/. This hard coded assumption had
not shown up before because
On 4/18/05, Michael G Schwern [EMAIL PROTECTED] wrote:
Try this, it should fix the tests under Win32. Let me know.
I changed $(... to \$( when I applied, and all tests pass.
IE:
\$(PERLRUN) $self-{PERL_SRC}/win32/bin/pl2bat.pl :
Yves
--
perl -Mre=debug -e
On 4/13/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Wed, Apr 13, 2005 at 09:21:48AM +0100, Steve Hay wrote:
Michael G Schwern wrote:
http://www.pobox.com/~schwern/src/ExtUtils-MakeMaker-6.28.tar.gz
Any ideas how to fix the current problems in bleadperl on Win32?:
On Apr 5, 2005 9:47 PM, Michael G Schwern [EMAIL PROTECTED] wrote:
NOTE:
make distclean is really just make realclean + distcheck. We're actually
having a discussion about this over on the mm list. Point is distclean
doesn't do any more actual cleaning than realclean it just checks itself
On Apr 6, 2005 11:43 AM, Steve Hay [EMAIL PROTECTED] wrote:
demerphq wrote:
On Apr 5, 2005 9:47 PM, Michael G Schwern [EMAIL PROTECTED] wrote:
NOTE:
make distclean is really just make realclean + distcheck. We're
actually
having a discussion about this over on the mm list. Point
On Apr 6, 2005 12:47 PM, Michael G Schwern [EMAIL PROTECTED] wrote:
On Wed, Apr 06, 2005 at 11:36:44AM +0200, demerphq wrote:
Just so you know this isnt true with the Win32 makefiles at all. From
perl/win32/Makefile i have extracted distclean and realclean:
Win32's distclean looks like its
On Apr 5, 2005 12:34 AM, Abigail [EMAIL PROTECTED] wrote:
On Mon, Apr 04, 2005 at 05:53:30PM -0400, Ronald J Kimball wrote:
On Tue, Apr 05, 2005 at 03:55:26AM +0800, Dan Jacobson wrote:
D Dan, maybe you should post what you're doing with our, BEGIN and END so
D we can give suggestions on
On Apr 4, 2005 6:28 PM, Steve Hay [EMAIL PROTECTED] wrote:
Ton Hospel wrote:
In article [EMAIL PROTECTED],
Steven Schubiger [EMAIL PROTECTED] writes:
On 07 Oct 2003 00:00:13 +0200, Slaven Rezic [EMAIL PROTECTED] wrote:
: CPAN.pm (invoked as cpan in the command shell) reports a
On Apr 5, 2005 12:25 AM, Michael G Schwern [EMAIL PROTECTED] wrote:
We're also secure enough to
know that there's some things awk and sed still do better.
Never having used Sed or Awk, im curious what you think they do
better? Should we have a little section somewhere When to use Awk or
Sed
On Mar 31, 2005 11:27 PM, Alexey Tourbin [EMAIL PROTECTED] wrote:
On Fri, Mar 25, 2005 at 09:31:56AM +0100, H.Merijn Brand wrote:
$ perl -e 'eval { /(?{die})/ }; print'
Segmentation fault
This has been solved between 5.8.5 and 5.8.6:
pc09:/home/merijn 103 perl5.8.5 -e 'eval {
1 - 100 of 185 matches
Mail list logo
