perl.perl5.porters Google Group

Re: warding against bytes.pm

2010-01-05T20:07:32Z

I have no problem with doing it that way.
John
______________________________ ________________
This email has been scanned by Netintelligence
[link]

Re: warding against bytes.pm

2010-01-05T19:43:47Z

I think this is idealistic. In my opinion, it's not practical to use Perl's
Unicode tools without understanding the implementation down to the C
representation, including the SVf_UTF8 flag and how to use Devel::Peek to
snoop it. Unicode glitches are just too hard to debug without such expertise.

Re: [perl #71854] 5.10.1: for-loop scoping discrepancy with local functions (local *Foo = sub {})

2010-01-05T19:38:07Z

Lexical variables aren't accessed via their name. Subs capture the variable
that is associated with the name when the sub is instantiated. This allows
for features such as module-scoped variables and closures. It's possible to
change the value of the variables, but it's always going to be the same
variable.

Re: warding against bytes.pm

2010-01-05T18:56:42Z

I think the problem here is that we think of characters in Perl being
in UTF-8. We need to get away from this idea and think of characters as
*CHARACTERS* they only become bytes when encoded into some other format
for transport out of the program.
So if you want to send UTF-8 to MySQL you need to take you string and

[perl #71854] 5.10.1: for-loop scoping discrepancy with local functions (local *Foo = sub {})

2010-01-05T12:59:07Z

DESCRIPTION
If variable is defined before sub, the $file variable should be seen. It
apperas that for-loop somehow alters the scope, although the loop
variable is defined *before* the for-loop.
TEST RESULTS
The $FILE variable, when assigned is seen in sub.
The $file variable, when not in for loop, when assigned is seen in sub.

Re: warding against bytes.pm

2010-01-05T18:12:09Z

For that purpose, what you need to know is the number of bytes that
you'll be sending to MySQL. This depends on the characters and how
you're encoding them for communication with MySQL, *not* on how Perl
is representing them internally. See previous messages about writing
UTF-8-encoded text to a file.

Re: warding against bytes.pm

2010-01-05T02:54:50Z

It is not.
A byte count can be very useful,
for example if you need to stay
within MySQL's max_allowed_packet
when creating big SQL statements.
sub bytes {
require bytes;
bytes::length($_[0]);
}

Re: [perl #71852] Warning "/* within comment" in Win32 config.h-related files

2010-01-05T17:44:00Z

kmx wrote:
That would miss the point of having the "/**/" at the end of the line.
The point of that is precisely so that the directive's state can be
switched by the minimal edit of adding or removing "/*" at the start.
If the "/* ... /**/" scheme is not to be used, then the inactive state
of the line should be something like

[perl #71852] Warning "/* within comment" in Win32 config.h-related files

2010-01-05T12:58:52Z

This is a bug report for perl from k...@volny.cz,
generated with the help of perlbug 1.39 running under perl 5.11.3.
------------------------------ ------------------------------ -----
[Please describe your issue here]
Hi,
I would like to propose a cosmetic fix to some "config.h-related" files
in perl core sources mostly regarding Win32 platform.

Re: rvalue "statement" given blocks

2010-01-05T17:03:43Z

Hi David,
* David Nicol <davidni...@gmail.com> [2010-01-05 17:45]:
No. And that isn’t even plausible if you consider two facts:
• In BASIC-PLUS, where the idea came from, modifiers are freely
stackable.
• If Larry didn’t *want* the restriction, why would he decide
that Perl 6, free from concerns of an existing implementation,

Smoke [5.11.3] v5.11.3-26-g1a64a5e FAIL(XF) openbsd 4.6 (i386/1 cpu)

2010-01-05T14:20:18Z

Automated smoke report for 5.11.3 patch 1a64a5e6c710ac493fe0339fdf240f 512a934369 v5.11.3-26-g1a64a5e
p5openbsd: AMD Athlon(tm) Processor ("AuthenticAMD" 686-class, 256KB L2 cache) (909 MHz) (i386/1 cpu)
on openbsd - 4.6
using cc version 3.3.5 (propolice)
smoketime 14 hours 57 minutes (average 1 hour 52 minutes)

Re: makefile thoughts

2010-01-05T11:08:53Z

Andy Dougherty <dough...@lafayette.edu> said:
I'm no expert either, but after buying myself a shiny new
quadcore PC, I've been parallelizing (or sometimes paralyzing)
some makefiles so I can move more than 1 CPU bar on the
system monitor. I often use the construct
@ARGV = qw( file1 file2 file6 ) if ((@ARGV == 0) && -t);

Re: [perl #71828] Tie::Hash::NamedCapture::FIRSTKEY(undef) segfaults

2010-01-05T11:01:02Z

Turns out that all the Tie::Hash::NamedCapture routines are similarly
crash-prone, and that a fix is fairly simple, so done in blead as commit
1d021cc8647e49fd860b50abddff99 a11b306e2e
Nicholas Clark

Re: rvalue "statement" given blocks

2010-01-05T10:55:30Z

"42.7% of all statistics are made up on the spot."
-- [link]
;-)
Regards,
Shlomi Fish

Re: qualify a todo item ?

2010-01-05T08:57:43Z

2010/1/4 Jim Cromie <jim.cro...@gmail.com>:
I documented that :
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -40,6 +40,9 @@ instead there is an intentionally simpler library,
F<t/test.pl>. However,
quite a few tests in F<t/> have not been refactored to use it. Refactoring
any of these tests, one at a time, is a useful thing TODO.