At 18:01 02/04/2005 +, you wrote:
Ron Blaschke <[EMAIL PROTECTED]> wrote:
> Or even:
> nmake win32-installer
> ?
> The Windows equivalent of "rpm" would be "msi".
Maybe then:
nmake win32-inno-installer
I agree with you, 'win32-inno-installer' is a better target name than 'setup'.
Do you w
Roger Hale <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch wrote:
>>
>> As @ARGS (or @IN_ARGS, @OUT_ARGS) is being stored in the context, and
>> that context is defacto the continuation, yes - a tail-call would
>> inherit this information.
>>
>> leo
> But as each tail-call supplies a new @ARGS, how c
Will Coleda <[EMAIL PROTECTED]> wrote:
> .sub main @MAIN
> $P0 = new Integer
> store_global "Foo", unicode:"Bar", $P0
> print "ok 1\n"
> .end
> It generates the error:
> unimplemented unicode
Yep. charset/unicode.c:compute_hash() *was* unimplemented.
leo
2005-04-03 Darren Duncan <[EMAIL PROTECTED]>
--
I am now pleased to announce the second developer release of my
Rosetta rigorous database portability library, currently featuring
the SQL::Routine module. (Considering the huge number of changes
s
Ron Blaschke <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch wrote:
>>> There's gotta be at least one element in the array. Not sure why this
>>> compiles on other platforms, though.
>> gcc hasn't problems with it. Dunno what the standard says.
> MS VC++ has an error code "C2466 - cannot allocate a
Will Coleda <[EMAIL PROTECTED]> wrote:
> .sub main @MAIN
> $S0 = unicode:"\"]\nif I3 == "
> .end
> Generates:
> encodings/utf8.c:277: failed assertion `i->bytepos < PObj_buflen(s) - 4'
Slightly wrong assert. I've moved it after the advance of the bytepos
now.
> 2) The fact that the diagnosti
The NCI signature char 'I' used to be the Parrot Interpreter. It's now
'J'. This frees 'I' for its new and more consistent meaning INTVAL.
Classes that use the newer METHOD syntax don't need a change. Old code
that uses enter_nci_method() and uses an Bnterpreter argument should
be changed to us
Yitzchak Scott-Thoennes wrote:
Since you ask...
An important part of kwalitee to me is that Makefile.PL / Build.PL run
successfully with stdin redirected to /dev/null (that is, that any
user interaction be optional).
>
Another is that a bug-reporting address or mechanism (e.g. clp.modules
or cpan
Tels wrote:
On Friday 01 April 2005 21:47, Walter Goulet wrote:
I've been in contact with the author of Net-SSLeay about testing his
module. One limitation I have to work with is that the module has to
work out of the box with perl 5.6.0 which doesn't include the
Test::Simple and Test::More modules
Thomas Klausner wrote:
I cannot check POD coverage because Pod::Coverage executes the code.
No it doesn't. That said, if you don't want to run the code you're
testing, you are, errm, limiting yourself rather badly.
--
David Cantrell
Hi!
On Mon, Apr 04, 2005 at 10:32:14AM +0100, David Cantrell wrote:
> Thomas Klausner wrote:
>
> >I cannot check POD coverage because Pod::Coverage executes the code.
>
> No it doesn't.
Yes, it does.
Pod::Coverage uses Devel::Symdump to get a list of all subs.
> That said, if you don't want t
Sorry for flattening out the level of the discussion, but ...
On Sun, 03 Apr 2005, Yitzchak Scott-Thoennes wrote:
> On Sat, Apr 02, 2005 at 10:43:57AM -0500, Ricardo SIGNES wrote:
> > * "David A. Golden" <[EMAIL PROTECTED]> [2005-04-02T05:27:18]
> > > Andy Lester wrote:
> > > >Why is there a scor
HaloO,
I'll just use what Paul Seamons wrote:
Consider:
method foo {
.do_one_thing
.and_another_thing
map { $_.do_something_with( .bar ) } .items;
# .bar worked on the invocant - not the items
.and_the_last_thing
}
because I don't have to invent examples
During class registration of classes that define a MMD_init table,
several new things happen:
1) a MultiSub PMC is created in the "__parrot_core" namespace once
2a) if there is just one MMD variant:
a NCI method is created in the classes namespace
2b) if there are more then one MMD variants
Currently, config/gen/makefiles/root.in says:
TOUCH = $(PERL) -e ${PQ}open(A,qq{>>$$_}) or die foreach @ARGV${PQ}
However, this fails for my source tree. I habitually leave
CVS-controlled files write-only until they are locally modified.
(This is "cvs -r" behavior, also triggered by expor
-BEGIN PGP SIGNED MESSAGE-
Moin,
On Monday 04 April 2005 11:32, David Cantrell wrote:
> Tels wrote:
> > On Friday 01 April 2005 21:47, Walter Goulet wrote:
> >> I've been in contact with the author of Net-SSLeay about testing his
> >> module. One limitation I have to work with is that the
On Mon, Apr 04, 2005 at 12:00:20PM -0400, Chip Salzenberg wrote:
> Currently, config/gen/makefiles/root.in says:
>
> TOUCH = $(PERL) -e ${PQ}open(A,qq{>>$$_}) or die foreach @ARGV${PQ}
>
> However, this fails for my source tree. I habitually leave
> CVS-controlled files write-only until t
On Mon, Apr 04, 2005 at 12:00:20PM -0400, Chip Salzenberg wrote:
> Currently, config/gen/makefiles/root.in says:
>
> TOUCH = $(PERL) -e ${PQ}open(A,qq{>>$$_}) or die foreach @ARGV${PQ}
>
> However, this fails for my source tree. I habitually leave
> CVS-controlled files write-only until t
Juerd wrote:
my $four := three;
Assuming you meant $three instead of three.
Indeed. Sorry.
my $five = 5;
$four = 4; # $one == 4 now?
No, $four (and thus $three, which it is bound to) is now 4. $three is a
reference, which is a value, which is now *replaced* with the new value.
OK. Then you need to
Howdy all,
While writing some new Pugs examples I came across another file reading
bug having to do with laziness. When a list is slurped from a
filehandle, then the file closed before the list is accessed, the list
seems to be empty. I believe this is because of how lazily Pugs
creates/evalua
I was playing about with the different methods that could be called on
built-in types:
pugs> my @n = (12, 13, 14)
undef
pugs> @n
(12, 13, 14)
pugs> @n.elems
3
As I understand, these methods are also built-in subs (operators?), so
that they can be called as such:
pugs> elems @n
3
What I found su
On Sun, Apr 03, 2005 at 05:28:44PM +0800, Autrijus Tang wrote:
: On Sat, Apr 02, 2005 at 09:32:12PM -0500, Stevan Little wrote:
: > I was writing tests for split(, ) and I stumbled upon this
: > bug:
: >
: > pugs -e 'split(rx:perl5//, "not good")'
: >
: > Will go into an infinite loop. I also tr
Will Coleda <[EMAIL PROTECTED]> wrote:
> cvsuser 05/04/04 07:13:43
> Fix calling signature so it's in line with leo's recent change of I->J.
>
> Index: parrotinterpreter.pmc
Argh. I must have again "fixed" parrotinterpreter.c - I do remember
these changes.
Thanks for the ci and sorry,
le
Thomas Sandlaß skribis 2005-04-04 18:50 (+0200):
> In particular what does &infix<=> do?
Depends. What does it mean? :)
Specifically, what is &infix, what is <=>?
> 'Scalar of Ref of Any' without dispatching to 'Ref of Int'. That means
References and aliasing should have nothing to do with type
For some reason, I keep typing :=: instead of =:=. Do other people
experience similar typo-habits with new operators?
One of my other Perl 6 typo-habits is <<^H^Hargh!^H^H^H^H^H«, but that's
because I like how « and » look, but can't yet easily type them.
Juerd
--
http://convolution.nl/maak_jue
Hi,
I remembered Damian saying that pick does not only work on junctions,
but on arrays and hashes, too (and I even found his posting :):
http://groups.google.com/groups?selm=420DB295.3000902%40conway.org).
Are the following assumptions correct?
my $junc = 1|2|3;
print $junc.pick; # "1", "2"
Juerd wrote:
For some reason, I keep typing :=: instead of =:=. Do other people
experience similar typo-habits with new operators?
One of my other Perl 6 typo-habits is <<^H^Hargh!^H^H^H^H^H«, but that's
because I like how « and » look, but can't yet easily type them.
Juerd
«»«»«»«»«»«»«»«»«»«»«»«»
Ingo Blechschmidt wrote:
I remembered Damian saying that pick does not only work on junctions,
but on arrays and hashes, too (and I even found his posting :):
http://groups.google.com/groups?selm=420DB295.3000902%40conway.org).
Are the following assumptions correct?
my $junc = 1|2|3;
print $junc.
On Mon, 2005-04-04 at 15:07, Sam Vilain wrote:
> «»«»«»«»«»«»«»«»«»«»«»«»«»! :-þ
>
> an excerpt from my xkb config...
I think we've been over this ground before, but if you use EMACS, you'll
find this handy:
http://www.cs.tut.fi/~jkorpela/emacs-iso.html
Of course, some of the sequences used m
On Mon, Apr 04, 2005 at 03:55:23PM -0400, Aaron Sherman wrote:
: but if you use vim or emacs inside a terminal, you'll want to make sure
: it's in iso-latin-1 mode (e.g. in gnome-terminal, you have to use the
: menu: "Terminal->Set Character Encoding")
If you going to that trouble, at least try yo
On Mon, 2005-04-04 at 16:41, Larry Wall wrote:
> On Mon, Apr 04, 2005 at 03:55:23PM -0400, Aaron Sherman wrote:
> : but if you use vim or emacs inside a terminal, you'll want to make sure
> : it's in iso-latin-1 mode (e.g. in gnome-terminal, you have to use the
> : menu: "Terminal->Set Character En
In a message dated Mon, 4 Apr 2005, Ingo Blechschmidt writes:
> What does pick return on hashes? Does it return a random value or a
> random pair? (I suppose returning a pair is more useful.)
I'd assume in all cases that pick returns an *alias*, and in the case of
hashes, an alias to the pair:
:set encoding=utf8
:set fileencoding=utf8
The first controls the display, the second file saves. Vim has to have been
compiled with multibyte support, though.
From: Aaron Sherman <[EMAIL PROTECTED]>
Date: Mon, 4 Apr 2005 17:01:58 -0400
To: Larry Wall <[EMAIL PROTECTED]>
Cc: Perl6 Language List
S06
http://dev.perl.org/perl6/synopsis/S06.html
under "Flattening argument lists" (which I hope will be renamed
"Spreading arrays used as arguments") says this is OK:
sub foo($x, $y, $z) {...}# expects three scalars
foo([EMAIL PROTECTED]); # okay: @onetothree flattened to
# New Ticket Created by Chip Salzenberg
# Please include the string: [perl #34669]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34669 >
The creators of flex were rather mean to go and change the internal
API without even
A Perl 5 user thinks of flattening a data structure as taking
something which is nested and "linearizing" it.
FOR EXAMPLE:
use Data::Hash::Flatten;
# NESTED DATA
my $a = { bill => { '5/27/96' => { 'a.dat' => 1, 'b.txt' => 2,
'c.lsp' => 3 } },
jimm => { '6/22/98' => { 'x.prl'
I'd assume you'd get an *alias* to a random pair:
# Test error-correction
for 1..$entropy_threshhold {
%hash.pick.value = rand $scribble_factor;
}
Trey
In a message dated Mon, 4 Apr 2005, Ingo Blechschmidt writes:
> Hi,
>
>
> I remembered Damian saying that pick does not only work on
In a message dated Mon, 4 Apr 2005, Ingo Blechschmidt writes:
> What does pick return on hashes? Does it return a random value or a
> random pair? (I suppose returning a pair is more useful.)
I'd assume in all cases that pick returns an *alias*, and in the case of
hashes, an alias to the pair:
Yikes. Sorry about the ressends... my email client kept dying and I
thought the mail was lost. Guess not. :-)
Trey
In a message dated Mon, 4 Apr 2005, Trey Harris writes:
> In a message dated Mon, 4 Apr 2005, Ingo Blechschmidt writes:
> > What does pick return on hashes? Does it return a rando
The first discussion of flattening had to do with a list of data being
flattened into an array.
Further down we see another different use of the word "flattening" :
http://dev.perl.org/perl6/synopsis/S06.html
section="Flattening lists">
The unary prefix operator * flattens its operand
--- Stevan Little wrote:
> Howdy all,
>
> While writing some new Pugs examples I came across another file reading
> bug having to do with laziness. When a list is slurped from a
> filehandle, then the file closed before the list is accessed, the list
> seems to be empty. I believe this is beca
At 04:00 PM 4/4/2005, via RT wrote:
# New Ticket Created by Chip Salzenberg
# Please include the string: [perl #34669]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34669 >
The creators of flex were rather mean to go and chan
Terrence Brannon skribis 2005-04-04 18:45 (+):
> So, to avoid confusion with the common understanding of flattening in
> Perl, perhaps it should be called spreading or distributing.
I agree.
Likewise, "slurping" is probably best explained as collecting.
Juerd
--
http://convolution.nl/maak_
# New Ticket Created by Will Coleda
# Please include the string: [perl #34672]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34672 >
Failed Test Stat Wstat Total Fail Failed List of Failed
-
Got another one!
This one is your basic parsing error, and hopefully easily fixed.
Basically the return statement will not work without a value to return,
unless you have a () after it (which I assume is not "correct" syntax,
but also not really "wrong" syntax (but I will leave that for the
lan
# New Ticket Created by Will Coleda
# Please include the string: [perl #34675]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34675 >
Trying to track down a different problem, I just did a fresh checkout on OS X
and got t
On 2005-04-01, George Nistorica <[EMAIL PROTECTED]> wrote:
>
> For commands that need more than one input (i.e. shell installers) you
> can use the Expect module, which you can use to test such programs, that
> wait your input for more than one time.
Thanks for the tip. It led me to Test::Expect,
On Monday 04 April 2005 06:34 pm, Juerd wrote:
> Terrence Brannon skribis 2005-04-04 18:45 (+):
> > So, to avoid confusion with the common understanding of flattening in
> > Perl, perhaps it should be called spreading or distributing.
>
> I agree.
>
> Likewise, "slurping" is probably best expla
On Mon, Apr 04, 2005 at 05:40:10PM +, Terrence Brannon wrote:
:
: A Perl 5 user thinks of flattening a data structure as taking
: something which is nested and "linearizing" it.
:
: FOR EXAMPLE:
:
: use Data::Hash::Flatten;
:
: # NESTED DATA
: my $a = { bill => { '5/27/96' => { 'a.dat'
Andrew Rodland skribis 2005-04-04 22:34 (-0400):
> > Likewise, "slurping" is probably best explained as collecting.
> I like this. I'd be tempted to suggest "scatter" / "gather", but that's
Gather is taken.
> probably a bit opaque to the average reader. How about describing them as
> "expand" /
On Mon, Apr 04, 2005 at 10:34:13PM -0400, Andrew Rodland wrote:
: On Monday 04 April 2005 06:34 pm, Juerd wrote:
: > Terrence Brannon skribis 2005-04-04 18:45 (+):
: > > So, to avoid confusion with the common understanding of flattening in
: > > Perl, perhaps it should be called spreading or di
51 matches
Mail list logo
