Steve Hay wrote:
Automated smoke report for 5.8.6 patch 23784
TANGAROA.uk.radan.com: Intel(R) Pentium(R) 4 CPU 2.00GHz(~1992 MHz) (x86/1
cpu)
onMSWin32 - WinXP/.Net SP1
using cl version 12.00.8804
smoketime 40 minutes 43 seconds (average 2 minutes 32.688 seconds)
folks,
attached patch does some much needed cleanup of OptreeCheck.pm
and the test files that use it.
1. OptreeCheck no longer uses Data::Dumper, so tests which skipped on
that are cleaned up
2. f_sort, f_map, optree_samples were TODOd for 5.8.6
cuz of blead changed opcodes
Op een grimmige winterdag (Friday 14 January 2005 02:49),schreef
[EMAIL PROTECTED]:
Automated smoke report for 5.9.2 patch 23792
FAFNER: VAX 7000-720 (VAX/2 cpu)
onopenvms - V7.2
using CC/DECC version 60490005
smoketime 3 hours 24 minutes (average 1 hour 42 minutes)
Hi,
I have another question. I am testing the attached Perl script which
uses $|.
On Linux, the first set of 5 prints will be buffered and output on the
screen appears after the total delay time of 5 seconds. After that
Perl
encounters $|=1 (auto flush ON). From here, the second set of
5
On Fri, Jan 14, 2005 at 09:09:33AM +, Steve Hay wrote:
Steve Hay wrote:
Automated smoke report for 5.8.6 patch 23784
TANGAROA.uk.radan.com: Intel(R) Pentium(R) 4 CPU 2.00GHz(~1992 MHz) (x86/1
cpu)
onMSWin32 - WinXP/.Net SP1
using cl version 12.00.8804
Automated smoke report for 5.9.2 patch 23800 on bsd/os - 4.1 (i386/1 cpu)
(fixit.xs4all.nl) using version
Report by Test::Smoke v1.18.09 (perl 5.00503) [3 hours 3 minutes]
O = OK F = Failure(s), extended report at the bottom
X = test(s) failed under TEST but not under harness
? = still running
At 12:05 PM +0100 1/14/05, Abe Timmerman wrote:
CC/DECC /Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj FLOAT/G_FLOAT/
Define=(VERSION=1.01,XS_VERSION=1.01)/Include=([--])/NoList
ATTRS.c
%DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters
\ATTRS\
%MMK-F-ERRUPD,
Nicholas Clark via RT wrote:
This doesn't seem to be directly related to the compilation failure you
report. I get that too, but I'm not yet sure why.
Just let me know if I can help with further information.
Jesper
--
Jesper Krogh, [EMAIL PROTECTED], JabberID: [EMAIL PROTECTED]
signature.asc
On Fri, 2005-01-14 at 11:31, Jonathan Stowe wrote:
On Thu, 2005-01-13 at 18:52, [EMAIL PROTECTED] wrote:
GetConsoleMode failed, LastError=|6| at blib\lib/Term/ReadKey.pm line 265.
END failed--call queue aborted.
NMAKE : fatal error U1077: 'C:\WINDOWS\system32\cmd.exe' : return code
Nicholas Clark wrote:
As is, there's 5.005threads related stuff in win32/config_sh.PL in maint,
so actually please could you do the integration, and work out the correct
way to resolve the small conflict? As I can't be sure I've got it right.
5.005 threads still builds on maint on Unix (and
Jonathan Stowe wrote:
On Fri, 2005-01-14 at 11:31, Jonathan Stowe wrote:
On Thu, 2005-01-13 at 18:52, [EMAIL PROTECTED] wrote:
GetConsoleMode failed, LastError=|6| at blib\lib/Term/ReadKey.pm line 265.
END failed--call queue aborted.
NMAKE : fatal error U1077:
Hello,
I'm pleased to announce, after a long time of development and
beta testing, the first official release in the new 0.05x
series of CPANPLUS. Below is the changelog from the last beta
release to this one.
You can get it from:
http://cpanplus.xs4all.nl/~kane/CPANPLUS-0.051.tar.gz
Or soon
On Fri, Jan 14, 2005 at 03:06:22PM +, Steve Hay wrote:
I'm not sure what the correct resolution to the config_sh.PL conflict
is. Currently, maint will omit Thread from $Config{dynamic_ext} and
$Config{known_extensions} if 5.005 threads are not used, although Thread
still gets built
Nicholas Clark wrote:
On Fri, Jan 14, 2005 at 03:06:22PM +, Steve Hay wrote:
I'm not sure what the correct resolution to the config_sh.PL conflict
is. Currently, maint will omit Thread from $Config{dynamic_ext} and
$Config{known_extensions} if 5.005 threads are not used, although
On Fri, Jan 14, 2005 at 04:13:29PM +, Steve Hay wrote:
I didn't know. So I tried. With ithreads:
oops. with 5005threads:
$ grep _ext config.sh
dynamic_ext='B ByteLoader Cwd DB_File Data/Dumper Devel/DProf Devel/PPPort
Devel/Peek Digest/MD5 Encode Fcntl File/Glob Filter/Util/Call
Nicholas Clark wrote:
On Fri, Jan 14, 2005 at 04:13:29PM +, Steve Hay wrote:
Given that I messed up the annotations, code that removes Thread from
dynamic_ext (but not known_extensions) when 5.005 threads are not in use
(alternatively, only puts it in when 5005 threads are in use) would
On Thu, Jan 13, 2005 at 09:24:16PM -, Nicholas Clark via RT [EMAIL
PROTECTED] wrote:
On Thu, Jan 13, 2005 at 01:56:33PM +, Nicholas Clark wrote:
I didn't know, but looking at the pack implementation, it's 'U', and only
'U':
Seems to be 'C' and 'U'
But C is documented as:
On Fri, Jan 14, 2005 at 04:37:22PM +, Steve Hay wrote:
OK, so I'll keep the code that drops Thread from dynamic_ext with
ithreads for consistency with Unix (although it doesn't make much sense
to me either since Threads is actually still being built). Probably
this (and the Unix case)
This isn't really a bug report, it's just the first demonstration
this year (in this forum) of my ignorance. I was poking around in
the debugger to see what kind of slop perl would tolerate in
floating point literals, and, after trying 3.e1 (which is 30,
of course) I tested the water with
This isn't really a bug report, it's just the first demonstration
this year (in this forum) of my ignorance. I was poking around in
the debugger to see what kind of slop perl would tolerate in
floating point literals, and, after trying 3.e1 (which is 30,
of course) I tested the water with
On Fri, Jan 14, 2005 at 04:37:22PM +, Steve Hay wrote:
Nicholas Clark wrote:
On Fri, Jan 14, 2005 at 04:13:29PM +, Steve Hay wrote:
Given that I messed up the annotations, code that removes Thread from
dynamic_ext (but not known_extensions) when 5.005 threads are not in use
# New Ticket Created by Lukas Mai
# Please include the string: [perl #33792]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=33792
Hi,
apologies in advance if you receive this mail twice.
Anyway, here's my test
On Fri, Jan 14, 2005 at 05:44:44PM -, Orton, Yves wrote:
Im prettys sure that Perl is evaluating -+-3.e- as 3 and then adding minus
one to it to get 2 and then using the constant folding optimization to turn
it into 2 at compile time. (Or something really close to that.)
E:\perl -e print
I'm loading a fairly large C++ library via XS, and about 1/1000 times I
run it (as close as I can average given how it's run) the program hangs,
immune to all signals but KILL and taking no CPU and nominal memory.
When I attach gdb and grab a back-trace, the dllib routines are calling
__xstat64.
Yitzchak Scott-Thoennes [EMAIL PROTECTED]:
Looks like a bug to me; 3e is not treated as a valid constant, but 3e- is:
Perl is looking for an exponential-format floating-point numeral. It
will succeed if it sees e followed by a digit or by a + or - sign.
So
3e-
is considered a valid
On Fri, Jan 14, 2005 at 05:48:10AM +0200, Jarkko Hietaniemi wrote:
Automated smoke report for 5.9.2 patch 23792
kosh.hut.fi: alpha/EV6.7 (667 MHz) (alpha EV6.7 (21264A)/4 cpu)
onosf1 - V5.1
using cc version V6.5-011
smoketime 5 hours 25 minutes (average 54 minutes 16
D You are reading too much into this. There is no mention of
D variable initialization, just variable declaration. my has nothing
D to do with what is placed in the variable.
Hmmm, then with perl -w
maybe we should get a warning at
my ($c,$f)=0;
because it doesn't do what we thought.
D If
D Cprint !!0 prints nothing because the false value returned by logical
D operators stringifies to the empty string.
OK, mention something like that on perlop then, as beginners can't
figure out what went wrong with print 0, !0, !!0.
D Perhaps you'd like to take a look at
D http://perlmonks.org/index.pl?node_id=322751
OK I will next time I dial up, but whatever is there ought to be
mentioned right there in perldoc -f split.
On Thu, Jan 13, 2005 at 07:48:04AM +0800, Dan Jacobson wrote:
As I don't know what
my ($c,$f)=0;
is doing, I am highly unqualified to make patches. All I can do is
make alerts about things that look weird to beginners.
It's doing what Perl always does on list assignment; the first element on
On Fri, Jan 14, 2005 at 11:04:20PM +, Dave Mitchell wrote:
On Thu, Jan 13, 2005 at 07:48:04AM +0800, Dan Jacobson wrote:
As I don't know what
my ($c,$f)=0;
is doing, I am highly unqualified to make patches. All I can do is
make alerts about things that look weird to beginners.
On Fri, 14 Jan 2005 15:33:07 -0800, Yitzchak Scott-Thoennes
[EMAIL PROTECTED] wrote:
The perldoc -f my documentation *could* use some work.
From a syntactic viewpoint, my($c, $f)=0 is a list assignment to the
return value of my(), but perlfunc doesn't discuss *what my returns*.
IMO it is
On Fri, Jan 14, 2005 at 06:38:03PM -0600, David Nicol wrote:
perldoc -f my is stunningly short, considering all the subtle confusion
that springs from my.
Most of the documentation for 'my' is in perlsub, in the section
'Private Variables via my()'
--
Standards (n). Battle insignia or
Dan Jacobson wrote:
D Cprint !!0 prints nothing because the false value returned by logical
D operators stringifies to the empty string.
OK, mention something like that on perlop then, as beginners can't
figure out what went wrong with print 0, !0, !!0.
Dan,
I highly recommend _Programming Perl,
34 matches
Mail list logo
