On Sun, Nov 02, 2003 at 12:20:11AM -0600, Andy Lester wrote:
> >>Anything that uses the C operator is a prime candidate for
> >>bugginess. Please keep an eye out for them as you do your testing.
> >>Any function that contains C oughta be heavily checked.
> >>
> >>Ditto anything that uses C or C wi
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #24396]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=24396 >
...
t\src\io..NOK 9# Failed test (t\src\io.t at line 242)
# go
The Perl 6 Summary of the week ending 20031102
It's Monday morning, the croissants have been baked, the focaccia is
glistening with all the extra virgin olive oil I poured on it as it left
the oven and, in the airing cupboard, a raisin borodinsky slouches
towards full proof (thought
Luke Palmer wrote:
So, we can have :: in names, but that doesn't represent any inherent
relationship between the module before the :: and the one after. I
think this is an important thing to keep.
However, will it be possible to, for example, do:
module Foo;
module Bar { ... }
And refer
Is it possible to get environment variables from perl6 programme? It
failes when I try to use perl5 hash %ENV. Thanks.
Whilst attempting to implement DBCS encoding, I have discovered that
skip_backward cannot be implemented for this encoding style, due to the
mixture of 1-byte and 2-byte characters.
Some of the available options:
1) Throw an exception if somebody tries to skip_backward in a DBCS
string
2) Stan
# New Ticket Created by Allison Randal
# Please include the string: [perl #24391]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=24391 >
Several tests in t/compiler/call.t were failing with the error:
set_integer_native(
# New Ticket Created by Allison Randal
# Please include the string: [perl #24392]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=24392 >
This patch changes the test instead of the code. The code is actually
correct. (We dec
In an attempt to understand what the plan is with regard to ICU and
Parrot strings in general, I've been gathering together links to
previous bits of discussion on:
http://www.vendian.org/parrot/wiki/bin/view.cgi/Main/
ParrotDistributionUnicodeSupport
Obviously what is still needed is
But rather than post emails with such guidelines, only for them to
be lost in the sands of time, wouldn't it be better to update the
web site?
Yeah, it would. I'd like to come up with a list of guidelines of
things to watch for. Lately, I've been spending my free time on prove
and Test::Harness
On Mon, Nov 03, 2003 at 02:06:01PM +, Tim Bunce wrote:
> A separate issue with C is that code using it generally assumes
> that the has itterator is at the start of the hash. If it's not
> (because an C loop somewhere terminated early, for example)
> then some items of the hash will be skipped.
At 14:06 + 11/3/03, Tim Bunce wrote:
Its cheap to reset an itterator, just do
keys %foo;
before the C loop.
Just wondering, is keys() optimized for void context? Perlfunc only states:
As a side effect, calling keys() resets the HASH⤁s internal iterator...
If it is _not_ optimized
Elizabeth Mattijsen wrote:
> Just wondering, is keys() optimized for void context? Perlfunc only states:
>
> As a side effect, calling keys() resets the HASHâ¤_s internal iterator...
Yes, it is.
> If keys() _is_ optimized for void context, a change in the
> perlfunc.pod seems to be in orde
At 17:51 +0100 11/3/03, Rafael Garcia-Suarez wrote:
Elizabeth Mattijsen wrote:
> Just wondering, is keys() optimized for void context? Perlfunc
only states:
> As a side effect, calling keys() resets the HASHâ¤_s internal
iterator...
Yes, it is.
Ok, so it is indeed "cheap"!
> If keys() _is
On Tue, Oct 28, 2003 at 05:33:09PM +, [EMAIL PROTECTED] wrote:
> Tim Bunce <[EMAIL PROTECTED]> wrote:
> > On Tue, Oct 28, 2003 at 02:37:29PM +, [EMAIL PROTECTED] wrote:
> >>
applied thanks.
/s
thanks, applied.
/s
Hello.
I have several questions about parrot dosc.
I have noticed that docs\parrot_assembly.pod is old version of
\docs\pdds\pdd06_pasm.pod file.
Will these files be distinguished in the future?
Catalog docs\ops is empty in 0.0.13 version.
Is it bug?
Nick.
On Mon, 3 Nov 2003, Nick Kostirya wrote:
> Hello.
> I have several questions about parrot dosc.
>
> I have noticed that docs\parrot_assembly.pod is old version of
> \docs\pdds\pdd06_pasm.pod file.
> Will these files be distinguished in the future?
And they're both wrong, unfortunately. :( pdd06
"Jürgen" "Bömmels" (via RT) <[EMAIL PROTECTED]> writes:
> The attached patch makes it an optional part of the normal build
> system. By using the switch --buildicu the ./configure of icu/source
> is run and the makefile is extended with rules for building and
> cleaning icu. This option is not ena
On Mon, 3 Nov 2003, Dan Sugalski wrote:
> On Mon, 3 Nov 2003, Nick Kostirya wrote:
>
> > Catalog docs\ops is empty in 0.0.13 version.
> > Is it bug?
>
> I think that's leftover cruft.
Well, we used to generate a .pod file for each .ops file, at build time,
which lived in here. However, we do
I've been playing with an "uncommitted" op version of invoke
that takes a method or sub by name like below:
invoke "foo", 0
The 0 is irrelevant to the eye, but it is a placeholder for the self-modifying
instruction. Upon call, invoke by name does:
op invoke(STR, INT)
PMC sub
if($2 == 0) {
sub =
Simon Glover <[EMAIL PROTECTED]> writes:
> On Mon, 3 Nov 2003, Dan Sugalski wrote:
>
> > On Mon, 3 Nov 2003, Nick Kostirya wrote:
> >
> > > Catalog docs\ops is empty in 0.0.13 version.
> > > Is it bug?
> >
> > I think that's leftover cruft.
>
> Well, we used to generate a .pod file for each .
# New Ticket Created by "Microsoft Network System"
# Please include the string: [perl #24400]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=24400 >
file attachment: gerb.exe
This e-mail in its original form contained one
[EMAIL PROTECTED] (Andrew Shitov) writes:
> Is it possible to get environment variables from perl6 programme? It
> failes when I try to use perl5 hash %ENV. Thanks.
Are you sure you're using the Perl 6 hash syntax? (%ENV{FOO} rather than Perl
5-style $ENV{FOO})
What version of Perl 6 are you usin
I tried this one-line programme for example:
my %e = %ENV;
and got this (parrot-0.0.13/perl are built under mandrake linux):
Global '_HV_ENV' not found
Error: '/parrot-0.0.13/parrot -r env.imc ' failed with exit code 1
Stopped at /parrot-0.0.13/languages/perl6/perl6 line 339
main::mydie(256,'/p
On Mon, Nov 03, 2003 at 09:33:56AM -0600, Andy Lester wrote:
> >But rather than post emails with such guidelines, only for them to
> >be lost in the sands of time, wouldn't it be better to update the
> >web site?
>
> Yeah, it would. I'd like to come up with a list of guidelines of
> things to wa
On 10/31/2003 8:08 AM, Andy Lester wrote:
>
> Personally, I find the POD useful when I'm going thru a Devel::Cover run. I
> interleave POD with functions and I like to refer to my docs.
Well, since POD is intended to be documentation (not code or even comments) it
seems reasonable to omit it from
On 11/3/2003 12:20 PM, Tim Bunce wrote:
> On Tue, Oct 28, 2003 at 05:33:09PM +, [EMAIL PROTECTED] wrote:
>>
>> Right now, if your cover_db holds data for a dozen files, but you test them
>> one at a time, you have to read and write *all* the coverage data (as well
>> as have the RAM to hold it
Personally, I find the POD useful when I'm going thru a Devel::Cover
run. I
interleave POD with functions and I like to refer to my docs.
Well, since POD is intended to be documentation (not code or even
comments) it
seems reasonable to omit it from a coverage report. That said, if I
can find a
On Sun, Nov 02, 2003 at 07:50:05PM -0700, Luke Palmer wrote:
: So, we can have :: in names, but that doesn't represent any inherent
: relationship between the module before the :: and the one after. I
: think this is an important thing to keep.
:
: However, will it be possible to, for example, do
Larry wrote:
In theory I suppose you could have objects with module attributes:
class Foo {
has module .Bar { ... }
}
Just don't ask me what it means...
Of course, Larry's just joking there...he knows precisely what it means.
It means that every object of class Foo has its own pr
Damian Conway wrote:
Larry wrote:
This kind of behaviour is more useful for nested classes, I suspect, but
it should certainly be available for nested modules as well.
So, what's the difference between a module and a class, and
why would you want dynamic namespaces? Isn't that something
you'd
33 matches
Mail list logo
