Re: [PATCH] POD typos

[Piotr Fusik]

On  6 Aug, Steven P. Schubiger wrote:

> On  6 Aug, Piotr Fusik wrote:
> >> >  A A text (ASCII) string, will be space padded.
> >> > -Z A null terminated (ASCIZ) string, will be null padded.
> >> > +Z A null terminated (ASCIIZ) string, will be null padded.
> >> >  b A bit string (ascending bit order inside each byte, like vec()).
> >>
> >> That isn't a typo.The change should be reversed.
> >>
> > It seems that both are used. I prefer ASCIIZ because it clearly contains 
> > "ASCII". 
> > What does ASCIZ stands for (i.e. which 'I' is dropped?)
> 
> According to [1] .ascii (e.g. ASCII) & .asciz (e.g. ASCIZ) are fairly common.
> I'm not too sure whether ASCIIZ is valid, since no reference could be found
> that would approve your point of view.
> 
> [1] http://www.objsw.com/docs/as_71.html
> 
Popularity of an assembler directive isn't a good argument here.
If it was, we'd say "2 + 2 equ 4" (or even "(2 add 2) equ 4").

And you referenced to just the GNU assembler. Other assemblers spell it 
".asciiz":

http://www.google.com/search?q=.asciiz


www.acronymfinder.com cointains neither ASCIZ or ASCIIZ.

[PATCH] Post-OSCON NN/NULLOK-ing

[Andy Lester]

Not a lot of excitement here.  More NN/NULLOK in embed.fnc.  Some
consting in op.c.

oxox,
Andy

-- 
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
diff -pur bleadperl/embed.fnc bw/trunk/embed.fnc
--- bleadperl/embed.fnc 2005-07-29 03:59:52.0 -0500
+++ bw/trunk/embed.fnc  2005-07-29 21:04:46.0 -0500
@@ -271,18 +271,18 @@ Ap|void   |gv_fullname|NN SV* sv|NN cons
 Apmb   |void   |gv_fullname3   |NN SV* sv|NN const GV* gv|NULLOK const char* 
prefix
 Ap |void   |gv_fullname4   |NN SV* sv|NN const GV* gv|NULLOK const char* 
prefix|bool keepmain
 Ap |void   |gv_init|NN GV* gv|HV* stash|NN const char* name|STRLEN 
len|int multi
-Apd|HV*|gv_stashpv |const char* name|I32 create
-Apd|HV*|gv_stashpvn|const char* name|U32 namelen|I32 create
-Apd|HV*|gv_stashsv |SV* sv|I32 create
-Apd|void   |hv_clear   |HV* tb
-Ap |void   |hv_delayfree_ent|HV* hv|HE* entry
-Apd|SV*|hv_delete  |HV* tb|const char* key|I32 klen|I32 flags
-Apd|SV*|hv_delete_ent  |HV* tb|SV* key|I32 flags|U32 hash
-ApdR   |bool   |hv_exists  |HV* tb|const char* key|I32 klen
-ApdR   |bool   |hv_exists_ent  |HV* tb|SV* key|U32 hash
-Apd|SV**   |hv_fetch   |HV* tb|const char* key|I32 klen|I32 lval
-Apd|HE*|hv_fetch_ent   |HV* tb|SV* key|I32 lval|U32 hash
-Ap |void   |hv_free_ent|NN HV* hv|NULLOK HE* entry
+Apd|HV*|gv_stashpv |NN const char* name|I32 create
+Apd|HV*|gv_stashpvn|NN const char* name|U32 namelen|I32 create
+Apd|HV*|gv_stashsv |NULLOK SV* sv|I32 create
+Apd|void   |hv_clear   |NULLOK HV* tb
+Ap |void   |hv_delayfree_ent|NN HV* hv|NULLOK HE* entry
+Apd|SV*|hv_delete  |NULLOK HV* tb|NN const char* key|I32 klen|I32 
flags
+Apd|SV*|hv_delete_ent  |NULLOK HV* tb|NN SV* key|I32 flags|U32 hash
+ApdR   |bool   |hv_exists  |NULLOK HV* tb|NN const char* key|I32 klen
+ApdR   |bool   |hv_exists_ent  |NULLOK HV* tb|NN SV* key|U32 hash
+Apd|SV**   |hv_fetch   |NULLOK HV* tb|NN const char* key|I32 klen|I32 
lval
+Apd|HE*|hv_fetch_ent   |NULLOK HV* tb|NN SV* key|I32 lval|U32 hash
+Ap |void   |hv_free_ent|NN HV* hv|NULLOK HE* entryK
 Apd|I32|hv_iterinit|NN HV* tb
 ApdR   |char*  |hv_iterkey |NN HE* entry|NN I32* retlen
 ApdR   |SV*|hv_iterkeysv   |NN HE* entry
@@ -440,13 +440,13 @@ p |int|magic_wipepack |SV* sv|MAGIC* mg
 p  |void   |magicname  |const char* sym|const char* name|I32 namlen
 Ap |void   |markstack_grow
 #if defined(USE_LOCALE_COLLATE)
-p  |int|magic_setcollxfrm|SV* sv|MAGIC* mg
-p  |char*  |mem_collxfrm   |const char* s|STRLEN len|STRLEN* xlen
+p  |int|magic_setcollxfrm|NN SV* sv|NN MAGIC* mg
+p  |char*  |mem_collxfrm   |NN const char* s|STRLEN len|NN STRLEN* xlen
 #endif
 Afp|SV*|mess   |NN const char* pat|...
 Ap |SV*|vmess  |NN const char* pat|NULLOK va_list* args
-p  |void   |qerror |SV* err
-Apd |void   |sortsv |SV ** array|size_t num_elts|SVCOMPARE_t cmp
+p  |void   |qerror |NN SV* err
+Apd|void   |sortsv |NN SV** array|size_t num_elts|SVCOMPARE_t cmp
 Apd|int|mg_clear   |NN SV* sv
 Apd|int|mg_copy|NN SV* sv|NN SV* nsv|const char* key|I32 klen
 pd |void   |mg_localize|NN SV* sv|NN SV* nsv
@@ -494,22 +494,22 @@ ApPa  |long   |my_htonl   |long l
 ApPa   |long   |my_ntohl   |long l
 #endif
 p  |void   |my_unexec
-Apa|OP*|newANONLIST|OP* o
-Apa|OP*|newANONHASH|OP* o
+Apa|OP*|newANONLIST|NULLOK OP* o
+Apa|OP*|newANONHASH|NULLOK OP* o
 Ap |OP*|newANONSUB |I32 floor|OP* proto|OP* block
 Apa|OP*|newASSIGNOP|I32 flags|NULLOK OP* left|I32 optype|NULLOK 
OP* right
 Apa|OP*|newCONDOP  |I32 flags|NN OP* first|NULLOK OP* 
trueop|NULLOK OP* falseop
 Apd|CV*|newCONSTSUB|NULLOK HV* stash|NULLOK const char* 
name|NULLOK SV* sv
 Ap |void   |newFORM|I32 floor|NULLOK OP* o|NULLOK OP* block
-Apa|OP*|newFOROP   |I32 flags|char* label|line_t forline \
-   |NULLOK OP* sv|OP* expr|OP*block|OP*cont
-Apa|OP*|newLOGOP   |I32 optype|I32 flags|OP* left|OP* right
-Apa|OP*|newLOOPEX  |I32 type|OP* label
-Apa|OP*|newLOOPOP  |I32 flags|I32 debuggable|OP* expr|OP* block
+Apa|OP*|newFOROP   |I32 flags|NULLOK char* label|line_t forline \
+   |NULLOK OP* sv|NN OP* expr|NULLOK OP* 
block|NULLOK OP* cont
+Apa|OP*|newLOGOP   |I32 optype|I32 flags|NN OP* left|NN OP* right
+Apa|OP*|newLOOPEX  |I32 type|NN OP* label
+Apa|OP*|newLOOPOP  |I32 flags|I32 debuggable|NULLOK OP* 
expr|NULLOK OP* block
 Apa|OP*|newNULLLIST
 Apa|OP*|newOP  |I32 optype|I32 flags
 Ap |void   

[PATCH] make threads.xs emit warnings properly

[Tassilo von Parseval]

Hi,

the attached patch wraps ckWARN_d around the Perl_warn calls in
threads.xs so that these default warnings can be switched off using "no
warnings 'threads'" or the -X switch. Also included the corresponding
changes to perldiag.pod.

I wasn't quite sure what to do with

Perl_warn(aTHX_ "CLONE %" SVf,obj);

For now I added ckWARN_d there, too. But I think a real and descriptive
warning message is needed there, something like "Attempt to clone
non-thread object" or so. Then again, I am not even sure this warning is
ever emitted.

Cheers,
Tassilo
-- 
use bigint;
$n=71423350343770280161397026330337371139054411854220053437565440;
$m=-8,;;$_=$n&(0xff)<<$m,,$_>>=$m,,print+chr,,while(($m+=8)<=200);
--- perl-current/ext/threads/threads.xs~2005-08-07 06:48:14.0 
+0200
+++ perl-current/ext/threads/threads.xs 2005-08-07 06:52:15.0 +0200
@@ -168,8 +168,9 @@ Perl_ithread_hook(pTHX)
 int veto_cleanup = 0;
 MUTEX_LOCK(&create_destruct_mutex);
 if (aTHX == PL_curinterp && active_threads != 1) {
-   Perl_warn(aTHX_ "A thread exited while %" IVdf " threads were running",
-   (IV)active_threads);
+   if (ckWARN_d(WARN_THREADS))
+   Perl_warn(aTHX_ "A thread exited while %" IVdf " threads were 
running",
+ (IV)active_threads);
veto_cleanup = 1;
 }
 MUTEX_UNLOCK(&create_destruct_mutex);
@@ -304,7 +305,7 @@ Perl_ithread_run(void * arg) {
  SV *sv = POPs;
  av_store(params, i, SvREFCNT_inc(sv));
}
-   if (SvTRUE(ERRSV)) {
+   if (SvTRUE(ERRSV) && ckWARN_d(WARN_THREADS)) {
Perl_warn(aTHX_ "thread failed to start: %" SVf, ERRSV);
}
FREETMPS;
@@ -566,14 +567,12 @@ Perl_ithread_self (pTHX_ SV *obj, char* 
 void
 Perl_ithread_CLONE(pTHX_ SV *obj)
 {
- if (SvROK(obj))
-  {
-   ithread *thread = SV_to_ithread(aTHX_ obj);
-  }
- else
-  {
-   Perl_warn(aTHX_ "CLONE %" SVf,obj);
-  }
+if (SvROK(obj)) {
+   ithread *thread = SV_to_ithread(aTHX_ obj);
+}
+else if (ckWARN_d(WARN_THREADS)) {
+   Perl_warn(aTHX_ "CLONE %" SVf,obj);
+}
 }
 
 AV*
--- perl-current/ext/threads/threads.pm~2005-08-07 07:07:12.0 
+0200
+++ perl-current/ext/threads/threads.pm 2005-08-07 07:07:39.0 +0200
@@ -50,7 +50,7 @@ our @EXPORT_OK = ( @{ $EXPORT_TAGS{'all'
 our @EXPORT = qw(
 async  
 );
-our $VERSION = '1.06';
+our $VERSION = '1.07';
 
 
 # || 0 to ensure compatibility with previous versions
--- perl-current/pod/perldiag.pod~  2005-08-07 06:52:24.0 +0200
+++ perl-current/pod/perldiag.pod   2005-08-07 06:54:01.0 +0200
@@ -193,7 +193,7 @@ know which context to supply to the righ
 
 =item A thread exited while %d threads were running
 
-(W) When using threaded Perl, a thread (not necessarily the main
+(W threads)(S) When using threaded Perl, a thread (not necessarily the main
 thread) exited while there were still other threads running.
 Usually it's a good idea to first collect the return values of the
 created threads by joining them, and only then exit from the main
@@ -3875,7 +3875,7 @@ target of the change to
 
 =item thread failed to start: %s
 
-(S) The entry point function of threads->create() failed for some reason.
+(W threads)(S) The entry point function of threads->create() failed for some 
reason.
 
 =item times not implemented
 

Smoke [5.9.3] 25272 FAIL(c) linux 2.6.12-6-686 [debian] (i686/1 cpu)

[steve]

Automated smoke report for 5.9.3 patch 25272
kirk: Intel(R) Celeron(R) CPU 2.00GHz (GenuineIntel 1994MHz) (i686/1 cpu)
onlinux - 2.6.12-6-686 [debian]
using ? unknown cc version 
smoketime 11 seconds (average 1.375 seconds)

Summary: FAIL(c)

O = OK  F = Failure(s), extended report at the bottom
X = Failure(s) under TEST but not under harness
? = still running or test results not (yet) available
Build failures during:   - = unknown or N/A
c = Configure, m = make, M = make (after miniperl), t = make test-prep

   25272 Configuration (common) none
--- -
c c 
c c -Duseithreads
c c -DPERL_DEBUG_COW
c c -DPERL_DEBUG_COW -Duseithreads
| +- -DDEBUGGING
+--- no debugging


MANIFEST declared 'ext/Encode/lib/Encode/MIME/Header/ISO_2022_JP.pm' but it is 
missing
MANIFEST declared 'ext/Encode/t/mime_header_iso2022jp.t' but it is missing

-- 
Report by Test::Smoke v1.19#716 running on perl 5.8.7
(Reporter v0.016 / Smoker v0.015)

Re: [Encode] 2.11 Relased!

[Rafael Garcia-Suarez]

On 8/5/05, Dan Kogai <[EMAIL PROTECTED]> wrote:
> I decided to finish my homework before I leave Portland.   That is,
> Encode-2.11.

Thanks, applied (with the PerlIO::encoding patch) as #25271.

Although you missed this chunk from bleadperl :

--- ext/Encode/encoding.pm  (révision 19732)
+++ ext/Encode/encoding.pm  (copie de travail)
@@ -402,7 +402,7 @@
 The multiple use of this pragma is discouraged.
 
 By the same reason, the use this pragma inside modules is also
-discouraged (though not as strongly discouraged as the case above.  
+discouraged (though not as strongly discouranged as the case above.  
 See below).
 
 If you still have to write a module with this pragma, be very careful

[perl #36819] Bleadperl: abs() busted outside integer range

[via RT]

# New Ticket Created by  Dominic Dunlop 
# Please include the string:  [perl #36819]
# in the subject line of all future correspondence about this issue. 
# https://rt.perl.org/rt3/Ticket/Display.html?id=36819 >


This is a bug report for perl from [EMAIL PROTECTED],
generated with the help of perlbug 1.35 running under perl vv5.9.3.


-
Bleadperl gets abs() wrong for all numbers larger than the narrower  
of INT_MAX
or the mantissa of a double.

This is not a compiler issue: I've tried both gcc-3.3 and 4.0.

For (32-bit) [EMAIL PROTECTED]:
$ ./miniperl -lwe 'print(abs) for (0, -1e-200 * 1e-200, 1, -1,
2**31, -2**31, 2**32, -2**32, 2**52, -2**52, 2**63, -2**63,
2**64, -2**64, 1e50, -1e50, 1e200*1e200, 1e200*-1e200);'
0
0
1
1
2147483648
2147483648
-4294967296
-4294967296
-4.5035996273705e+15
-4.5035996273705e+15
-9.22337203685478e+18
-9.22337203685478e+18
-1.84467440737096e+19
-1.84467440737096e+19
-1e+50
-1e+50
-inf
-inf

For perl5.8.7:
0
0
1
1
2147483648
2147483648
4294967296
4294967296
4.5035996273705e+15
4.5035996273705e+15
9.22337203685478e+18
9.22337203685478e+18
1.84467440737096e+19
1.84467440737096e+19
1e+50
1e+50
inf
inf

For a slightly down-rev 64-bit perl ([EMAIL PROTECTED]):
0
0
1
1
2147483648
2147483648
4294967296
4294967296
4503599627370496
4503599627370496
-9.22337203685478e+18
-9.22337203685478e+18
-1.84467440737096e+19
-1.84467440737096e+19
-1e+50
-1e+50
-inf
-inf

-
---
Flags:
 category=core
 severity=medium
---
Site configuration information for perl vv5.9.3:

Configured by domo at Sat Aug  6 12:39:59 CEST 2005.

Summary of my perl5 (revision 5 version 9 subversion 3 patch 25269)  
configuration:
   Platform:
 osname=darwin, osvers=8.2.0, archname=darwin-thread-multi-2level
 uname='darwin tullamore.local 8.2.0 darwin kernel version 8.2.0:  
fri jun 24 17:46:54 pdt 2005; root:xnu-792.2.4.obj~3release_ppc power  
macintosh powerpc '
 config_args='-de -Doptimize=-g -Dusethreads -Dusedevel'
 hint=recommended, useposix=true, d_sigaction=define
 usethreads=define useithreads=define usemultiplicity=define
 useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
 use64bitint=undef use64bitall=undef uselongdouble=undef
 usemymalloc=n, bincompat5005=undef
   Compiler:
 cc='cc', ccflags ='-fno-common -DPERL_DARWIN -no-cpp-precomp - 
DDEBUGGING -fno-strict-aliasing -pipe -Wdeclaration-after-statement - 
I/usr/local/include',
 optimize='-g',
 cppflags='-no-cpp-precomp -fno-common -DPERL_DARWIN -no-cpp- 
precomp -DDEBUGGING -fno-strict-aliasing -pipe -Wdeclaration-after- 
statement -I/usr/local/include'
 ccversion='', gccversion='4.0.0 (Apple Computer, Inc. build  
5026)', gccosandvers=''
 intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=4321
 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
 ivtype='long', ivsize=4, nvtype='double', nvsize=8,  
Off_t='off_t', lseeksize=8
 alignbytes=8, prototype=define
   Linker and Libraries:
 ld='env MACOSX_DEPLOYMENT_TARGET=10.3 cc', ldflags =' -L/usr/ 
local/lib'
 libpth=/usr/local/lib /usr/lib
 libs=-ldbm -ldl -lm -lc
 perllibs=-ldl -lm -lc
 libc=/usr/lib/libc.dylib, so=dylib, useshrplib=false,  
libperl=libperl.a
 gnulibc_version=''
   Dynamic Linking:
 dlsrc=dl_dlopen.xs, dlext=bundle, d_dlsymun=undef, ccdlflags=' '
 cccdlflags=' ', lddlflags=' -bundle -undefined dynamic_lookup -L/ 
usr/local/lib'

Locally applied patches:


---
@INC for perl vv5.9.3:
 lib
 /sw/lib/perl5
 /sw/lib/perl5/darwin
 /usr/local/lib/perl5/5.9.3/darwin-thread-multi-2level
 /usr/local/lib/perl5/5.9.3
 /usr/local/lib/perl5/site_perl/5.9.3/darwin-thread-multi-2level
 /usr/local/lib/perl5/site_perl/5.9.3
 /usr/local/lib/perl5/site_perl
 .

---
Environment for perl vv5.9.3:
 DYLD_LIBRARY_PATH (unset)
 HOME=/Users/domo
 LANG (unset)
 LANGUAGE (unset)
 LD_LIBRARY_PATH (unset)
 LOGDIR (unset)
 PATH=/Users/domo/bin:/usr/local/bin:/sw/bin:/sw/sbin:/bin:/sbin:/ 
usr/bin:/usr/sbin:/usr/X11R6/bin
 PERL5LIB=/sw/lib/perl5:/sw/lib/perl5/darwin
 PERL5_CPANPLUS_CONFIG=/sw/lib/perl5/site_perl/5.8.4/CPANPLUS/ 
Config.pm
 PERL_BADLANG (unset)
 SHELL=/bin/bash

-- 
Dominic Dunlop

Smoke [5.9.0] 21539 FAIL(m) openbsd 3.6 (i386/1 cpu)

[Steven P. Schubiger]

Automated smoke report for 5.9.0 patch 21539
accognoscere.homeunix.org: AMD Athlon(TM) XP 1800+ ("AuthenticAMD" 686-class) 
(i386/1 cpu)
onopenbsd - 3.6
using cc version 2.95.3 20010125 (prerelease, propolice)
smoketime 3 minutes 32 seconds (average 26.500 seconds)

Summary: FAIL(m)

O = OK  F = Failure(s), extended report at the bottom
X = Failure(s) under TEST but not under harness
? = still running or test results not (yet) available
Build failures during:   - = unknown or N/A
c = Configure, m = make, M = make (after miniperl), t = make test-prep

   21539 Configuration (common) none
--- -
m - m - 
m - m - -Duse64bitint
m - m - -Duseithreads
m - m - -Duseithreads -Duse64bitint
| | | +- PERLIO = perlio -DDEBUGGING
| | +--- PERLIO = stdio  -DDEBUGGING
| +- PERLIO = perlio
+--- PERLIO = stdio


-- 
Report by Test::Smoke v1.19#716 running on perl 5.8.5
(Reporter v0.016 / Smoker v0.015)

Re: [PATCH] POD typos

[Steven P. Schubiger]

On  6 Aug, Piotr Fusik wrote:
>> >  A A text (ASCII) string, will be space padded.
>> > -Z A null terminated (ASCIZ) string, will be null padded.
>> > +Z A null terminated (ASCIIZ) string, will be null padded.
>> >  b A bit string (ascending bit order inside each byte, like vec()).
>>
>> That isn't a typo.The change should be reversed.
>>
> It seems that both are used. I prefer ASCIIZ because it clearly contains 
> "ASCII". 
> What does ASCIZ stands for (i.e. which 'I' is dropped?)

According to [1] .ascii (e.g. ASCII) & .asciz (e.g. ASCIZ) are fairly common.
I'm not too sure whether ASCIIZ is valid, since no reference could be found
that would approve your point of view.

[1] http://www.objsw.com/docs/as_71.html

-- 
Steven P. Schubiger <[EMAIL PROTECTED]> http://sts.accognoscere.org/
They say a little knowledge is a dangerous thing, but it's not one half 
so bad as a lot of ignorance. -- Terry Pratchett

Re: [PATCH] New test of IEEE floating point peculiarities

[Piotr Fusik]

> (If somebody can point me at a user-visible way
> in Perl of extracting the sign from an NV other than by stringifying  
> it, I'd love to hear about it.)

On Windows:
perl -le "print unpack'H*',pack'F',-0.0"
0080

On big-endians it will probably be:
8000

Re: [PATCH] Compress::Zlib 1.36

[Abe Timmerman]

Op een mooie zomerdag (Saturday 06 August 2005 00:12),schreef  Paul Marquess:
> This is mostly VMS fixes. Standalone version has just been uploaded to
> CPAN.
>
> Could someone on please try building & testing 1.36 on VMS using the CPAN
> release please?

$mms test
(cleaned up output)
t/01version.  ok
t/02zlib  ok
t/03examples  FAILED tests 8-13
Failed 6/13 tests, 53.85% okay
t/04encoding  ok
t/05gzsetp..  ok
t/06gzdopen.  
   Can't call method "gzwrite" on an undefined value at t/06gzdopen.t line 66.

%C-F-EINVAL, invalid argument
dubious
Test returned status 3506356 (wstat 1024, 0x400)
(VMS status is 3506356)
DIED. FAILED tests 3-23
Failed 21/23 tests, 8.70% okay
Failed TestStat Wstat Total Fail  Failed  List of Failed
---
t/03examples.t   136  46.15%  8-13
t/06gzdopen.t   350  102423   41 178.26%  3-23
Failed 2/6 test scripts, 66.67% okay. 27/302 subtests failed, 91.06% okay.
%C-F-EINVAL, invalid argument
%MMS-F-ABORT, For target TEST_DYNAMIC, CLI returned abort status: %X003580B4.
-C-F-EINVAL, invalid argument

The C<$Inc> code in t/03examples.t is still not right (attached patch fixes 
that):
$ perl -"Mblib" [.t]03examples.t
1..13
not ok 1
# Failed test at line 119
not ok 2
# Failed test at line 120
not ok 3
# Failed test at line 130
not ok 4
# Failed test at line 132
not ok 5
# Failed test at line 150
not ok 6
# Failed test at line 151
Can't locate Compress/Zlib.pm in @INC (@INC contains: perl_root:
[lib.VMS_AXP.5_8
_6] perl_root:[lib] perl_root:[lib.site_perl.VMS_AXP] perl_root:
[lib.site_perl]
/perl_root/lib/site_perl .) at ./examples/filtdef line 6.
BEGIN failed--compilation aborted at ./examples/filtdef line 6.
%SYSTEM-W-NOSUCHFILE, no such file

Running the failing test(10) from the command line shows:
(The "define/user sys$*put ..." are a VMS way for shell's < and > redirection)

$ type hello1.gz
hello
this is
a test
message
x t
xuu
the end
$ define/user sys$input hello1.gz
$ define/user sys$output hello2.gz
$ perl -"Mblib" [.examples]gzstream
Cannot open stdout: invalid argument
%C-F-EINVAL, invalid argument

That means gzopen() failes :-(
Same goes for t/06gzdopen.t. I'm afraid I can't help here as know no C and 
nothing about the OpenVMS CRTL.

Patch also adds better cleanup of tempfiles and checked on OS X, Win32, VMS.

HTH +
Good luck,

Abe
-- 
N-IS> Hmm - those block comments all look similar to me!
They sure do look alike-- but I didn't feel that ambitious. Someone else may.
   -- Jarkko Hietaniemi on p5p @ 2002-10-24

diff -ru CZ136orig/t/03examples.t CZ136/t/03examples.t
--- CZ136orig/t/03examples.tFri Aug  5 23:40:27 2005
+++ CZ136/t/03examples.tSat Aug  6 11:31:52 2005
@@ -40,18 +40,7 @@
 }
  
 
-my $Inc = '' ;
-#if ($^O eq 'VMS') {
-#  $Inc = '-"I[.blib.lib]" -"I[.blib.arch]"';
-#}
-if ($^O eq 'MSWin32') {
-  foreach (@INC)
-   { $Inc .= qq["-I$_" ]}
-} 
-else {
-  foreach (@INC)
-   { $Inc .= "-I$_ " }
-} 
+my $Inc = join " ", map qq["-I$_"] => @INC;
 
 my $Perl = '' ;
 $Perl = ($ENV{'FULLPERL'} or $^X or 'perl') ;
@@ -170,5 +159,6 @@
 ok(13, $b eq $hello1 ) ;
 }
 
-
-unlink $file1, $file2, $stderr ;
+END {
+for ($file1, $file2, $stderr) { 1 while unlink $_ } ;
+}
diff -ru CZ136orig/t/03examples.t CZ136/t/03examples.t
--- CZ136orig/t/03examples.t	Fri Aug  5 23:40:27 2005
+++ CZ136/t/03examples.t	Sat Aug  6 11:31:52 2005
@@ -40,18 +40,7 @@
 }
  
 
-my $Inc = '' ;
-#if ($^O eq 'VMS') {
-#  $Inc = '-"I[.blib.lib]" -"I[.blib.arch]"';
-#}
-if ($^O eq 'MSWin32') {
-  foreach (@INC)
-   { $Inc .= qq["-I$_" ]}
-} 
-else {
-  foreach (@INC)
-   { $Inc .= "-I$_ " }
-} 
+my $Inc = join " ", map qq["-I$_"] => @INC;
 
 my $Perl = '' ;
 $Perl = ($ENV{'FULLPERL'} or $^X or 'perl') ;
@@ -170,5 +159,6 @@
 ok(13, $b eq $hello1 ) ;
 }
 
-
-unlink $file1, $file2, $stderr ;
+END {
+for ($file1, $file2, $stderr) { 1 while unlink $_ } ;
+}

Re: [EMAIL PROTECTED] on OpenVMS still not building

[John E. Malmberg]

John E. Malmberg wrote:

John E. Malmberg wrote:


Abe Timmerman wrote:


Hi all,

The build stops here:

Running Mkbootstrap for B::C ()
MCR BLDROOT:[00]miniperl.exe "-I[---.lib]" "-I[---.lib]" 
"-MExtUtils::Comman

d" -e chmod 644 C.BS
MCR BLDROOT:[00]miniperl.exe "-I[---.lib]" "-I[---.lib]" 
"-MExtUtils::Comman

d" -e cp C.bs [---.LIB.AUTO.B.C]C.BS
MCR BLDROOT:[00]miniperl.exe "-I[---.lib]" "-I[---.lib]" 
"-MExtUtils::Comman

d" -e chmod 644 [---.LIB.AUTO.B.C]C.BS
%MMS-F-ABORT, For target SUBDIRS, CLI returned abort status: %X10EE8180.
%MMS-F-ABORT, For target DYNEXT, CLI returned abort status: %X10EE8034.


I pulled down a new copy of blead-perl last night, but the .patch file 
did not get transferred at that time so I do not know what number it is.
That is due to a bug in my experimental implementation if rsync that I 
have not had time to code a fix for.


At this time blead-perl is 25270.

I applied all the patches that I have pending + an additional untested 
patch for converting VMS status codes to UNIX errno values.


I could not reproduce this build problem.

Currently I have 26 test scripts failing, and I think I know the reasons 
for at least 5 of them so far.


-John
[EMAIL PROTECTED]
Personal Opinion Only

Re: sysread corrupts strings

[Jeff 'japhy' Pinyan]

On Aug 6, Torsten Foertsch said:


[EMAIL PROTECTED]:~> perl -MData::Dumper -e '
 open F, "/dev/null" and
   sysread F, $buf, 1024, 1024;
 print length $buf, "\n", Dumper($buf), ($buf ne ""), "\n"
'
1024
$VAR1 = '';
1

I am reading 0 bytes into $buf at offset 1024. After that $buf is an empty
string with a length of 1024 that is not equal to an empty string. I would
have expected $buf to be a string of 1024 \0 bytes.


The string ISN'T empty, it's just that you're not seeing the null 
characters because they're not being displayed in a way your terminal 
understands.  Run your program through 'cat -vet', and you'll see that the 
1024 NULLs are there.  Or set one of those Data::Dumper variables that 
controls the visual output.


--
Jeff "japhy" Pinyan %  How can we ever be the sold short or
RPI Acacia Brother #734 %  the cheated, we who for every service
http://japhy.perlmonk.org/  %  have long ago been overpaid?
http://www.perlmonks.org/   %-- Meister Eckhart

Re: [perl #969] shifting of bitvecs considered broken

[Rafael Garcia-Suarez]

On 8/6/05, Jarkko Hietaniemi <[EMAIL PROTECTED]> wrote:
> 
> How is the fixing of lexical pragmas progressing?  If there were
> a working solution for that, I could implement a pragma for shifting
> of scalars as bitvecs.

I've an unfinished patch, and I've planned to work on this after the
next 5.9.x is released. (Development plans are to be explained in my
OSCON talk slides, which I've to put on line soon. Must wait to be
home to do that, though, due to my server having crashed or
something.)

Re: [PATCH] Re: [PATCH] Re: [perl #36819] perlbug AutoReply: Bleadperl: abs() busted outside integer range

[H.Merijn Brand]

On Sat, 6 Aug 2005 17:47:40 +0200, Dominic Dunlop <[EMAIL PROTECTED]>
wrote:

> On 2005–08–06, at 17:03, H.Merijn Brand wrote:
> > If I look at the patch, wouldn't it be an idea to take the  
> > opportunity to
> > make the test less count sentitive?
> >
> > +# Give abs() a good work-out before using it in anger
> > +tryeq 5, abs(0), 0;
> > +tryeq 6, abs(1), 1;
> > +tryeq 7, abs(-1), 1;
> >
> > =>
> >
> > +# Give abs() a good work-out before using it in anger
> > +tryeq $T++, abs(0), 0;
> > +tryeq $T++, abs(1), 1;
> > +tryeq $T++, abs(-1), 1;
> 
> Good point.
> >
> > Or do you want the count indicators to be easily traceable?
> 
> There is that. No. Let's make the thing more maintainable. Reworked  
> replacement for complete patch attached.

Thanks, applied as change #25270

> > Or is this test too basic to rely on $T++?
> >
> Nah. base.lex.t does exactly what you suggest, so we can rely on it  
> by the time we hit anything in comp.


-- 
H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/)
using Perl 5.6.2, 5.8.0, 5.8.5, & 5.9.2  on HP-UX 10.20, 11.00 & 11.11,
 AIX 4.3 & 5.2, SuSE 9.2 & 9.3, and Cygwin. http://www.cmve.net/~merijn
Smoking perl: http://www.test-smoke.org,perl QA: http://qa.perl.org
 reports  to: [EMAIL PROTECTED],perl-qa@perl.org

[PATCH] Re: [PATCH] Re: [perl #36819] perlbug AutoReply: Bleadperl: abs() busted outside integer range

[Dominic Dunlop]

On 2005–08–06, at 17:03, H.Merijn Brand wrote:
If I look at the patch, wouldn't it be an idea to take the  
opportunity to

make the test less count sentitive?

+# Give abs() a good work-out before using it in anger
+tryeq 5, abs(0), 0;
+tryeq 6, abs(1), 1;
+tryeq 7, abs(-1), 1;

=>

+# Give abs() a good work-out before using it in anger
+tryeq $T++, abs(0), 0;
+tryeq $T++, abs(1), 1;
+tryeq $T++, abs(-1), 1;


Good point.


Or do you want the count indicators to be easily traceable?


There is that. No. Let's make the thing more maintainable. Reworked  
replacement for complete patch attached.



Or is this test too basic to rely on $T++?

Nah. base.lex.t does exactly what you suggest, so we can rely on it  
by the time we hit anything in comp.

--
Dominic Dunlop



abs_patch
Description: Binary data

Re: [PATCH] Re: [perl #36819] perlbug AutoReply: Bleadperl: abs() busted outside integer range

[H.Merijn Brand]

On Sat, 6 Aug 2005 16:31:37 +0200, Dominic Dunlop <[EMAIL PROTECTED]>
wrote:

> [As I write, this bug report has yet to hit p5p. I hope this follow- 
> up follows it to the list. Anyway ...]
> 
> I wrote:
> > Bleadperl gets abs() wrong for all numbers larger than the narrower  
> > of INT_MAX
> > or the mantissa of a double.

If I look at the patch, wouldn't it be an idea to take the opportunity to
make the test less count sentitive?

+# Give abs() a good work-out before using it in anger
+tryeq 5, abs(0), 0;
+tryeq 6, abs(1), 1;
+tryeq 7, abs(-1), 1;

=>

+# Give abs() a good work-out before using it in anger
+tryeq $T++, abs(0), 0;
+tryeq $T++, abs(1), 1;
+tryeq $T++, abs(-1), 1;

Or do you want the count indicators to be easily traceable?
Or is this test too basic to rely on $T++?

> > This is not a compiler issue: I've tried both gcc-3.3 and 4.0.
> >
> > For (32-bit) [EMAIL PROTECTED]:
> > $ ./miniperl -lwe 'print(abs) for (0, -1e-200 * 1e-200, 1, -1,
> > 2**31, -2**31, 2**32, -2**32, 2**52, -2**52, 2**63, -2**63,
> > 2**64, -2**64, 1e50, -1e50, 1e200*1e200, 1e200*-1e200);'
> > 0
> > 0
> > 1
> > 1
> > 2147483648
> > 2147483648
> > -4294967296
> > -4294967296
> > -4.5035996273705e+15
> > -4.5035996273705e+15
> > -9.22337203685478e+18
> > -9.22337203685478e+18
> > -1.84467440737096e+19
> > -1.84467440737096e+19
> > -1e+50
> > -1e+50
> > -inf
> > -inf
> 
> The problem is a slip-up in the constification of pp.c. I attach a  
> patch to fix it, and to add tests for abs() to op/arith.t. I also  
> took the opportunity to soften the test script's hard dependency on  
> Config.pm. (The patch is larger than it deserves to be because abs()  
> needs testing early, and all the hardwired test numbers thereafter  
> needed to change.)


-- 
H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/)
using Perl 5.6.2, 5.8.0, 5.8.5, & 5.9.2  on HP-UX 10.20, 11.00 & 11.11,
 AIX 4.3 & 5.2, SuSE 9.2 & 9.3, and Cygwin. http://www.cmve.net/~merijn
Smoking perl: http://www.test-smoke.org,perl QA: http://qa.perl.org
 reports  to: [EMAIL PROTECTED],perl-qa@perl.org

[PATCH] New test of IEEE floating point peculiarities

[Dominic Dunlop]

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 floating-point peculiarites: infinity, not-a-number,  
negative

#   zero. Based on information from 
#   with thanks.
#
#   Not applicable to architectures where floating-point does not follow
#   the IEEE standard -- see the comment "Add your architecture  
here ...".

...

The tests are intended to exercise the underlying floating point  
hardware and library support; I've tried to steer clear of stuff  
that's already tested in op/sprintf.t. This proved impossible for  
"negative zero", and consequently there's a skip for certain  
architectures round some tests that require that negative zero is  
stringified as "-0". (If somebody can point me at a user-visible way  
in Perl of extracting the sign from an NV other than by stringifying  
it, I'd love to hear about it.) And of course everything's skipped  
for non-IEEE floating point.


The patch I just submitted to fix abs() (bug #36819) is a prerequisite.

The patch does not update MANIFEST. Should it?
--
Dominic Dunlop




ieeefp-patch
Description: Binary data

sysread corrupts strings

[Torsten Foertsch]

Hi,

is that a known feature?

[EMAIL PROTECTED]:~> perl -MData::Dumper -e '
  open F, "/dev/null" and 
sysread F, $buf, 1024, 1024; 
  print length $buf, "\n", Dumper($buf), ($buf ne ""), "\n"
'
1024
$VAR1 = '';
1

I am reading 0 bytes into $buf at offset 1024. After that $buf is an empty 
string with a length of 1024 that is not equal to an empty string. I would 
have expected $buf to be a string of 1024 \0 bytes.

tested with 5.8.3, 5.8.5 and 5.8.6.

Torsten


pgpQtk3CYGt26.pgp
Description: PGP signature

[PATCH] Re: [perl #36819] perlbug AutoReply: Bleadperl: abs() busted outside integer range

[Dominic Dunlop]

[As I write, this bug report has yet to hit p5p. I hope this follow- 
up follows it to the list. Anyway ...]


I wrote:
Bleadperl gets abs() wrong for all numbers larger than the narrower  
of INT_MAX

or the mantissa of a double.

This is not a compiler issue: I've tried both gcc-3.3 and 4.0.

For (32-bit) [EMAIL PROTECTED]:
$ ./miniperl -lwe 'print(abs) for (0, -1e-200 * 1e-200, 1, -1,
2**31, -2**31, 2**32, -2**32, 2**52, -2**52, 2**63, -2**63,
2**64, -2**64, 1e50, -1e50, 1e200*1e200, 1e200*-1e200);'
0
0
1
1
2147483648
2147483648
-4294967296
-4294967296
-4.5035996273705e+15
-4.5035996273705e+15
-9.22337203685478e+18
-9.22337203685478e+18
-1.84467440737096e+19
-1.84467440737096e+19
-1e+50
-1e+50
-inf
-inf


The problem is a slip-up in the constification of pp.c. I attach a  
patch to fix it, and to add tests for abs() to op/arith.t. I also  
took the opportunity to soften the test script's hard dependency on  
Config.pm. (The patch is larger than it deserves to be because abs()  
needs testing early, and all the hardwired test numbers thereafter  
needed to change.)

--
Dominic Dunlop



abs_patch
Description: Binary data

Re: IO::Socket::INET problems on FreeBSD

[Graham Barr]

On Aug 4, 2005, at 4:37 PM, Thomas Belote wrote:


Creating a new IO::Socket::INET always returns undef in FreeBSD
5.4-RELEASE-p2 and 5.4-RELEASE on i386.





For example the following code fails:
#!/usr/bin/perl -w
use IO::Socket;
$sock = IO::Socket::INET->new(PeerAddr => 'localhost:http(80)');


You shoud look in $@ when you get undef to determine why it failed

  die $@ unless $sock;

Graham.


print "opened : " . $sock . "\n";
print $sock "GET / HTTP/1.1\r\nHost: localhost\r\n\r\n";
while(<$sock>) { print ; }


However, I have found that my Ubuntu linux box works with the same  
CPAN
and IO::Socket:INET versions. So I believe this problem is with  
FreeBSD

in particular.

Re: [perl #36766] perldoc pollutes TEMP

[Randy W. Sims]

Demerphq wrote:

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 this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36766 >


This is a bug report for perl from [EMAIL PROTECTED],
generated with the help of perlbug 1.35 running under perl v5.8.7.


-

It seems that perldoc creates temporary files in \WINDOWS\TEMP,
but doesn't delete them upon exit.


This is not a bug.



Actually it IS a bug. Even if its a known bug deliberately left in place.


Actually, it is not. It is explicitly planned & coded behaviour. ;)



Ok, ok, its a bug^Wfeature. :-)
 


It may not be the preferred solution, but it is apparent that a choice
was made and that the code behaves as it was intended.



As Vadim says, its a design bug, not an implementation bug. But IMO
its still a bug. Or at the very least its a nasty kludge.


An unneccessary one it seems. I was wrong about the problem with file 
locking, or at least Sean's rewrite eliminated that problem. The 
following script used in place of `perldoc` works perfectly fine and 
behaves as requested, cleaning up after its self. It works with the 
default pager on Windows as well as with less. It even works when piped 
through groff with the '-n groff' option (although there is a bug that 
wont allow the pod2man script to be found because it is called 
pod2man.bat on MSWin32). This is on Windows 2000.


#!/usr/bin/perl -w

BEGIN {
$ENV{PERLDOCDEBUG} = 9;
$ENV{TEMP} = 'C:\\Temp';
#delete( $ENV{PAGER} );
}

use Pod::Perldoc;
$Pod::Perldoc::Temp_File_Lifetime = 0;

exit( Pod::Perldoc->run() );

__END__

Smoke [5.9.3] 25269 FAIL(XF) bsd/os 4.1 (i386/1 cpu)

[kane]

Automated smoke report for 5.9.3 patch 25269
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 54 minutes (average 1 hour 57 minutes)

Summary: FAIL(XF)

O = OK  F = Failure(s), extended report at the bottom
X = Failure(s) under TEST but not under harness
? = still running or test results not (yet) available
Build failures during:   - = unknown or N/A
c = Configure, m = make, M = make (after miniperl), t = make test-prep

   25269 Configuration (common) none
--- -
F F - - -Duse64bitint
X O - - 
| | | +- PERLIO = perlio -DDEBUGGING
| | +--- PERLIO = stdio  -DDEBUGGING
| +- PERLIO = perlio
+--- PERLIO = stdio


Failures: (common-args) none
[stdio/perlio] -Duse64bitint
../t/op/int.t...FAILED 11

[stdio] 
Inconsistent test results (between TEST and harness):
../lib/ExtUtils/t/Command.t.FAILED at test 9

-- 
Report by Test::Smoke v1.19_67 build 842 running on perl 5.00503
(Reporter v0.019 / Smoker v0.023)

Re: Smoke [5.9.3] 25263 FAIL(F) cygwin_nt-5.0 1.5.18(0.132/4/2) (x86/1 cpu)

[H.Merijn Brand]

On Wed, 3 Aug 2005 13:00:42 +0200, "H.Merijn Brand" <[EMAIL PROTECTED]>
wrote:

> On Wed, 3 Aug 2005 08:55 +0200, "H.Merijn Brand" <[EMAIL PROTECTED]>
> wrote:
> 
> > Automated smoke report for 5.9.3 patch 25263
> > pc03: x86 Family 15 Model 1 Stepping 2, GenuineIntel (x86/1 cpu)
> > oncygwin_nt-5.0 - 1.5.18(0.132/4/2)
> > using gcc version 3.4.4 (cygming special) (gdc 0.12, using dmd
> > 0.125) smoketime 8 hours 52 minutes (average 1 hour 6 minutes)
:
> > ../ext/POSIX/t/sigaction.t..FAILED 30
> > ../t/io/fs.tFAILED 18
> 
> I have no clue what to do about these two remaining failures.
> I was so very happy when I got Cygwin back to full 'O'

Cygwin guru's, please comment on this finding:

Current status:

ok 14 - open a
ok 15 - fchmod
ok 16 - perm reset
ok 17 - fchmod
not ok 18 - perm restored
# Failed at t/io/fs.t line 177
#  got '292'
# expected '438'
ok 19 - fchown

Status after
--8<---
--- t/io/fs.t.org   2005-08-06 13:22:38.587451200 +0200
+++ t/io/fs.t   2005-08-06 13:23:03.843768000 +0200
@@ -173,7 +173,7 @@ SKIP: {
 $mode = (stat "a")[2];
 is($mode & 0777, 0, "perm reset");
 is(chmod($newmode, "a"), 1, "fchmod");
-$mode = (stat $fh)[2];
+$mode = (stat "a")[2];
 is($mode & 0777, $newmode, "perm restored");
 }

-->8---

ok 14 - open a
ok 15 - fchmod
ok 16 - perm reset
ok 17 - fchmod
ok 18 - perm restored
ok 19 - fchown

The chmod call succeeded, but was not promoted to the file handle, but I
don't expect that to happen, since the chmod is called on "a", not on $fh

If I change the calls to
--8<---
--- t/io/fs.t.org   2005-08-06 13:22:38.587451200 +0200
+++ t/io/fs.t   2005-08-06 13:26:31.492352000 +0200
@@ -172,7 +172,7 @@ SKIP: {
 is(chmod(0, $fh), 1, "fchmod");
 $mode = (stat "a")[2];
 is($mode & 0777, 0, "perm reset");
-is(chmod($newmode, "a"), 1, "fchmod");
+is(chmod($newmode, $fh), 1, "fchmod");
 $mode = (stat $fh)[2];
 is($mode & 0777, $newmode, "perm restored");
 }
-->8---

ok 14 - open a
ok 15 - fchmod
ok 16 - perm reset
ok 17 - fchmod
ok 18 - perm restored
ok 19 - fchown

-- 
H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/)
using Perl 5.6.2, 5.8.0, 5.8.5, & 5.9.2  on HP-UX 10.20, 11.00 & 11.11,
 AIX 4.3 & 5.2, SuSE 9.2 & 9.3, and Cygwin. http://www.cmve.net/~merijn
Smoking perl: http://www.test-smoke.org,perl QA: http://qa.perl.org
 reports  to: [EMAIL PROTECTED],perl-qa@perl.org

Re: [perl #969] shifting of bitvecs considered broken

[Jarkko Hietaniemi]

> 
> But on the other hand Larry could see the argumentation my way too,
> that it should be possible to use <<= and >>= as bit shifters (looking
> at it from the C heritage it is strange that & | ~ ^ operate on strings
> as they were bitvectors, but the shift ops don't).  So an unfortunate
> murky corner of the dual (strings and numbers), err, trefoil (strings
> and bitvectors and numbers), err, quatrefoil (byte strings and Unicode
> strings and bitvectors and numbers) nature of Perl strings.
> 
> How to solve this, if this is to be solved?  *I* see as an ugly
> asymmetry blemish, but since enraged hordes of people have not
> ascended upon yes over all these years, I think I am in a minority,
> and I can live with it.  *IF* someone wants to fix this, maybe a pragma.
> Or maybe borgify Bit::Vector :-)

How is the fixing of lexical pragmas progressing?  If there were
a working solution for that, I could implement a pragma for shifting
of scalars as bitvecs.

-- 
Jarkko Hietaniemi <[EMAIL PROTECTED]> http://www.iki.fi/jhi/ "There is this 
special
biologist word we use for 'stable'.  It is 'dead'." -- Jack Cohen

RE: [PATCH] warning wrongly tagged as fatal error in perldiag.pod

[Paul Marquess]

From: ethan [mailto:[EMAIL PROTECTED]

> On Fri, Aug 05, 2005 at 05:31:27PM +0200 Rafael Garcia-Suarez wrote:
> > On 8/5/05, Tassilo von Parseval <[EMAIL PROTECTED]>
> wrote:
> 
> > > Other than that, this 'thread failed to start' warning is really hard
> to
> > > get rid of. Should any of the warnings in perldiag.pod be immune to
> even
> > > the -X switch, as this one is?
> >
> > No, they shouldn't. And C code should use ckWARN_d to emit them. (iirc)
> 
> There's also ckWARN which is used by threads::shared. What is the
> difference between ckWARN and ckWARN_d? It looks as if ckWARN
> additionally checks that $^W != 0 and should therefore be preferred over
> ckWARN_d.

ckWARN_d is for warnings that are enabled by default.

ckWARN is for warnings that need to be explicitly enabled with "use
warnings" or -w/W.

Paul

Re: Dtrace provider for perl?

[Alan Burlison]

Robert Spier wrote:

The speaker at OSCON (name escapes me, and I'm somewhere over Northern 
California watching cloud to cloud lighting) who talked about dtrace 
(and demonstrated php) seems to have done some digging into this.  He 
mentioned that "doing this for perl will not be easy".


Bryan Cantrill si the chap and as Dave already pointed out, he's right 
;-)  However it is far from impossible, and I think it is worth having a go.


--
Alan Burlison
--

Re: [PATCH] warning wrongly tagged as fatal error in perldiag.pod

[Tassilo von Parseval]

On Fri, Aug 05, 2005 at 05:31:27PM +0200 Rafael Garcia-Suarez wrote:
> On 8/5/05, Tassilo von Parseval <[EMAIL PROTECTED]> wrote:

> > Other than that, this 'thread failed to start' warning is really hard to
> > get rid of. Should any of the warnings in perldiag.pod be immune to even
> > the -X switch, as this one is?
> 
> No, they shouldn't. And C code should use ckWARN_d to emit them. (iirc)

There's also ckWARN which is used by threads::shared. What is the
difference between ckWARN and ckWARN_d? It looks as if ckWARN
additionally checks that $^W != 0 and should therefore be preferred over
ckWARN_d. 

Cheers,
Tassilo
-- 
use bigint;
$n=71423350343770280161397026330337371139054411854220053437565440;
$m=-8,;;$_=$n&(0xff)<<$m,,$_>>=$m,,print+chr,,while(($m+=8)<=200);

Re: [PATCH] POD typos

[Piotr Fusik]

> >  A A text (ASCII) string, will be space padded.
> > -Z A null terminated (ASCIZ) string, will be null padded.
> > +Z A null terminated (ASCIIZ) string, will be null padded.
> >  b A bit string (ascending bit order inside each byte, like vec()).
>
> That isn't a typo.The change should be reversed.
>
It seems that both are used. I prefer ASCIIZ because it clearly contains 
"ASCII". What does ASCIZ stands for (i.e. which 'I' is
dropped?)