Hi,
This is Rajarshi expressing Sastry's viewpoints since he's on vacation.
SADAHIRO Tomoyuki [EMAIL PROTECTED] wrote:
On Wed, 10 Aug 2005 14:06:56 +0530, Sastry wrote
As suggested by you, I ran the following script which resulted in
substituting all the characters with X
On Wed, 10 Aug 2005 23:47:47 -0400, John E. Malmberg [EMAIL PROTECTED]
wrote:
These are patches to t/run/exit.t and t/op/exec.t to go with change #25280.
I missed including them on that patch.
Thanks, applied as change #25283
Thanks also for the rather verbose comments you added there.
On Wed, 10 Aug 2005 23:26:03 -0400, John E. Malmberg [EMAIL PROTECTED]
wrote:
Second try:
Thanks, that applied clean as change #25283
Here are some miscellaneous VMS specific things that need to be fixed
for VMS to work with the VMS C Run-Time Library (CRTL) UNIX filename
mode that do not
On Wed, Aug 10, 2005 at 12:21:49PM -0400, Ed Ravin wrote:
I submit that this is a design bug - no other syslog() library behaves
this way, especially not the C library that Syslog.pm is based on.
Sys::Syslog::syslog() should return an error and let the user deal
with it (which would be an
On Sat, Aug 06, 2005 at 04:58:53PM +0200, Dominic Dunlop wrote:
Following on from perlbug #36676, which concerned perl's handling of
a peculiarity of IEEE-standard floating point, I've attached a patch
that creates a new test script, op/t/ieeefp.t:
# ieeefp.t
#
# Tests IEEE
Hi All,
I am learning how to use XS (C).
Firstly, I wrote a simple C++ class, compiled to libtest.so. A simple
main proved the test lib works fine.
test.h---
#ifndef _TEST_H
#define _TEST_H
class Test
{
public:
Test();
On 2005–08–11, at 11:05, Yitzchak Scott-Thoennes wrote:
The PERL_PRESERVE_IVUV stuff can lose a negative zero.
$ perl -we'$x = -.0; $x *= 1.0; print $x'
0
$ perl -we'$x = -.0; $x *= 1.1; print $x'
-0
Should a negative zero never get IOK turned on?
Certainly not in the case above. In the
On Thu, Aug 11, 2005 at 02:05:20AM -0700, Yitzchak Scott-Thoennes wrote:
The PERL_PRESERVE_IVUV stuff can lose a negative zero.
$ perl -we'$x = -.0; $x *= 1.0; print $x'
0
$ perl -we'$x = -.0; $x *= 1.1; print $x'
-0
Should a negative zero never get IOK turned on?
I meant to show the
On 2005–08–11, at 05:55, Dongxu Ma wrote:
I am learning how to use XS (C).
You may get more help by joining and posting to the perlxs list (see
http://lists.cpan.org/showlist.cgi?name=perl-xs) or perhaps to
perlmonks.org web site: the perl5-porters list is mainly concerned
with the
On Thu, Aug 11, 2005 at 03:31:11AM -0700, Yitzchak Scott-Thoennes wrote:
On Thu, Aug 11, 2005 at 02:05:20AM -0700, Yitzchak Scott-Thoennes wrote:
The PERL_PRESERVE_IVUV stuff can lose a negative zero.
$ perl -we'$x = -.0; $x *= 1.0; print $x'
0
$ perl -we'$x = -.0; $x *= 1.1; print $x'
Automated smoke report for 5.9.3 patch 25282
fixit.xs4all.nl: Pentium II (i386/1 cpu)
onbsd/os - 4.1
using cc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
smoketime 3 hours 56 minutes (average 1 hour 58 minutes)
Summary: FAIL(F)
O = OK F = Failure(s), extended
On Thu, Aug 11, 2005 at 03:57:27AM -0700, Yitzchak Scott-Thoennes wrote:
Even worse:
$ perl -we'$x = -.0; scalar(1.1 * $x); print $x'
0
'scuse my ignorance, but why is it important to preserve the sign on
floating zeroes?
--
A walk of a thousand miles begins with a single step...
then
Steve Hay wrote:
Automated smoke report for 5.9.3 patch 25260
ati4: Intel(R) Pentium(R) 4 CPU 2.80GHz(~2793 MHz) (x86/2 cpu)
onMSWin32 - WinXP/.Net SP2
using bcc32 version 5.5.1
smoketime 39 minutes 42 seconds (average 19 minutes 51 seconds)
Summary: FAIL(F)
On Thu, 11 Aug 2005 12:51:57 +0100, Dave Mitchell [EMAIL PROTECTED] wrote:
On Thu, Aug 11, 2005 at 03:57:27AM -0700, Yitzchak Scott-Thoennes wrote:
Even worse:
$ perl -we'$x = -.0; scalar(1.1 * $x); print $x'
0
'scuse my ignorance, but why is it important to preserve the sign on
On 2005–08–11, at 13:51, Dave Mitchell wrote:
'scuse my ignorance, but why is it important to preserve the sign on
floating zeroes?
On a scale of ten, its importance might crawl as high as a two. I
think it's mainly there so that, when something gets rounded to zero,
you can tell what side
On Wed, Aug 10, 2005 at 09:56:37PM -0500, Graham Barr wrote:
On Aug 10, 2005, at 4:43 PM, Nicholas Clark wrote:
which somewhat makes sense, as the #! for dprofpp, h2ph and h2xs is
#!/Users/nick/Sandpit/frob/spong
eval 'exec /Users/nick/Sandpit/blead25277/bin/perl5.9.3 -S $0
Perl can act as a /bin/sh replacement, re-dispatching based on the #! line.
The code to do this fires if #! doesn't contain perl, and a few other
conditions. Specifically, s is a pointer to the #! line:
if (!d
*s == '#'
ipathend ipath
On Wed, 10 Aug 2005 23:56:31 -0700 (PDT), rajarshi das [EMAIL PROTECTED] wrote
Hi,
This is Rajarshi expressing Sastry's viewpoints since he's on vacation.
SADAHIRO Tomoyuki [EMAIL PROTECTED] wrote:
According to the above statement in perlebcdic.pod,
s/[\x89-\x91]/X/g must substitute
I missed this one going by.
//depot/perl/lib/Test/Harness/Straps.pm#26 (text)
@@ -356,7 +356,6 @@
my $self = shift;
return $ENV{HARNESS_PERL} if defined $ENV{HARNESS_PERL};
-return MCR $^Xif $self-{_is_vms};
What's the purpose of this
Andy Lester wrote:
I missed this one going by.
//depot/perl/lib/Test/Harness/Straps.pm#26 (text)
@@ -356,7 +356,6 @@
my $self = shift;
return $ENV{HARNESS_PERL} if defined $ENV{HARNESS_PERL};
-return MCR $^Xif $self-{_is_vms};
What's
On Thu, Aug 11, 2005 at 12:50:39PM -0400, John E. Malmberg wrote:
The explicit call for the MCR shell is not needed in this case on
OpenVMS. The VMS.C code will add it in if needed when it actually runs
the child, and the VMS.C code knows to automatically vmsify() the command.
Is this a
Michael G Schwern wrote:
On Thu, Aug 11, 2005 at 12:50:39PM -0400, John E. Malmberg wrote:
The explicit call for the MCR shell is not needed in this case on
OpenVMS. The VMS.C code will add it in if needed when it actually runs
the child, and the VMS.C code knows to automatically vmsify()
The patch that I submitted is needed to eliminate a data corruption
issue that should be affecting more than just VMS.
If I have diagnosed this wrong, please let me know.
In VMS this data corruption is only visible in one apparent test script
where it causes Perl to exit with an access
On Thu, Aug 11, 2005 at 01:52:35AM -0700, Nicholas Clark via RT wrote:
On Wed, Aug 10, 2005 at 12:21:49PM -0400, Ed Ravin wrote:
I submit that this is a design bug - no other syslog() library behaves
this way, especially not the C library that Syslog.pm is based on.
Sys::Syslog::syslog()
John E. Malmberg wrote:
The patch that I submitted is needed to eliminate a data corruption
issue that should be affecting more than just VMS.
If I have diagnosed this wrong, please let me know.
just a wild conjecture from the peanut gallery.
There are some pretty subtle tricks played in
25 matches
Mail list logo
