Autrijus Tang wrote:
On Tue, May 10, 2005 at 11:11:12AM -0500, [EMAIL PROTECTED] wrote:
Please excuse the possible 'out of left field' (as we say) aspect of this
question but I recently heard about Omniscient Debugging (ODB):
http://www.lambdacs.com/debugger/debugger.html
Sounds very powerful
This
At 09:43 10/05/2005 +, you wrote:
> 1) On MinGW, can't execute miniparrot.exe during building
> Invoking Parrot to generate runtime/parrot/include/config.fpmc --cross your
> fingers
> ./miniparrot.exe config_lib.pasm > runtime/parrot/include/config.fpmc
> '.' is not recognized as an internal or
At 13:55 06/05/2005 -0700, you wrote:
t\op\debuginfo.t 5 1280 85 62.50% 4-8
Consider the last version of my patch attached to [perl #35083].
Francois.
~jerry
debuginfo.patch
Description: Binary data
Dhevendran K wrote:
Hi,
When I am building PERL 5.6.1 on Linux 2.6 Kernel AMD 64 bit machine [i.e.
"SUSE LINUX Enterprise Server 9 (x86_64) - Kernel 2.6.5-7.97-default (1)" ],
I am getting the following errors.
[snip]
lib/io_multihomedInvalid argument at lib/io_multihomed.t line 108.
Conn
Juerd <[EMAIL PROTECTED]> wrote:
> := is the thing that implements subroutine arguments. Ask yourself the
> same question with:
>
> sub another_routine ($rv) {
> ...
> }
> another_routine(some_routine());
>
> I'd expect $rv to be an alias to a copy of $foo's value, 42.
Really?
This works:
rule name { Larry | Matz | Guido }
rule project { Perl | Ruby | Python }
rule description { \s does \s }
'Larry does Perl' ~~ //; # true
'Larry does Java' ~~ //; # false
This too:
class Point {
has $.x;
has $.y;
method show () {
On Tue, May 10, 2005 at 05:24:30PM -0400, Rick Delaney wrote:
: On Tue, May 10, 2005 at 06:20:44AM -0600, Luke Palmer wrote:
: > Yeah, they're lexical, just like in Perl 5.
:
: Not just like Perl 5, I hope. If it was then the above would print
: "d".
Yes, Perl 5 actually uses an autolocalizing f
I have a "working" pugscc and cannot run the test suite. Should I
check in my pugscc changes or post them to the list so that Gaal can
run them against a Pugs that has a working test suite?
Rob
On 5/10/05, Gaal Yahas <[EMAIL PROTECTED]> wrote:
> On Tue, May 10, 2005 at 10:00:45AM -0400, Rob Kinyo
On Tue, May 10, 2005 at 11:11:12AM -0500, [EMAIL PROTECTED] wrote:
> Please excuse the possible 'out of left field' (as we say) aspect of this
> question but I recently heard about Omniscient Debugging (ODB):
> http://www.lambdacs.com/debugger/debugger.html
This seems to require almost the same j
On Tue, May 10, 2005 at 06:20:44AM -0600, Luke Palmer wrote:
> On 5/10/05, Ingo Blechschmidt <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > sub foo() {
say $1;# undef?
> > "abc" ~~ /^(.)/; # $1 now "a"
> > }
> >
> > sub bar() {
> > "def" ~~ /^(.)/; # $1 now "d"
On Tue, May 10, 2005 at 05:08:49PM +0200, Jens Rieks wrote:
> On Monday 09 May 2005 07:53, Patrick R. Michaud wrote:
> > The attached patch file adjusts C to always return false
> > for offsets beyond the end of the string, and updates
> > t/op/string_cclass.t to test this.
> Thanks, applied!
>
>
Hi,
Please excuse the possible 'out of left field' (as we say) aspect of this
question but I recently heard about Omniscient Debugging (ODB):
http://www.lambdacs.com/debugger/debugger.html
There is an article in the latest Dr Dobbs (6/05) by the above fellow (Bil
Lewis - former Sun scientist an
On Tue, May 10, 2005 at 10:00:45AM -0400, Rob Kinyon wrote:
> > Until we find a champion for that cause, I think it would still be useful
> > to allow pugs to be built, as today, on Windows using Cygwin's gcc and
> > perl5 (just like Corion makes a native build with -- I think -- cc1.exe
> > and a
On Tuesday 10 May 2005 20:29, Patrick R. Michaud wrote:
> On Tue, May 10, 2005 at 05:08:49PM +0200, Jens Rieks wrote:
> > On Monday 09 May 2005 07:53, Patrick R. Michaud wrote:
> > > The attached patch file adjusts C to always return false
> > > for offsets beyond the end of the string, and updates
On Tue, 2005-05-10 at 15:52, Joshua Gatcomb wrote:
> I am wondering what the proper behavior of binding to a sub's return
> value should be
>
> sub some_routine {
> my $foo = 42;
> return $foo;
> }
> my $rv := some_routine();
>
> Should $rv be bound to $foo or to a copy of $foo? I ask be
Joshua Gatcomb skribis 2005-05-10 15:52 (-0400):
> sub some_routine {
> my $foo = 42;
> return $foo;
> }
> my $rv := some_routine();
> Should $rv be bound to $foo or to a copy of $foo? I ask because with
> state() and closures, it makes a difference since the value can
> change.
:= is the
I am wondering what the proper behavior of binding to a sub's return
value should be
sub some_routine {
my $foo = 42;
return $foo;
}
my $rv := some_routine();
Should $rv be bound to $foo or to a copy of $foo? I ask because with
state() and closures, it makes a difference since the value
Thomas Sandlaß skribis 2005-05-10 19:02 (+0200):
> Juerd wrote:
> > No, again, please do not make the mistake of thinking VALUES have
> > identity. VARIABLES (containers) do. A reference points to a container,
> > never to a value directly.
> I don't consider it a mistake.
That is a problem.
> S
as part of both the pugs and mod_parrot effort, i've started working on
bringing the embedding and extending interfaces into the modern parrot
era. i'd like to start by adding public APIs (Parrot_*) where necessary
and adding missing prototypes to the headers. this will clean things up
without ch
Juerd wrote:
No, again, please do not make the mistake of thinking VALUES have
identity. VARIABLES (containers) do. A reference points to a container,
never to a value directly.
I don't consider it a mistake. So, you dany identity to "fat" values
like database connections or GUI objects?
This is s
Ashley, this is a great post. I have included it almost verbatim in my
p6 talk I'm giving tomorrow at our Perl Monger's meeting:
http://www.metaperl.com/talks/p6/hangman-elucidated/slide6.html
I hope you don't mind.
> On 5/5/05, Terrence Brannon <[EMAIL PROTECTED]> wrote:
>> I was looking at
Luke Palmer <[EMAIL PROTECTED]> writes:
> On 5/5/05, Terrence Brannon <[EMAIL PROTECTED]> wrote:
>> I was looking at a line in the hangman program:
>>
>> @letters == @solution.grep:{ $_ ne '' };
>>
>> and was told that I was looking at an adverbial block.
>
> The adverbial block is what you're g
> [EMAIL PROTECTED] - Tue May 10 06:00:52 2005]:
[cc'ed to our list, ticket #35392 ]
> Dear Perl eating Parrots,
>
> I hope you are the appropriate person to send this email to.
Almost :) Please use perl6-internals@perl.org for replies or questions
about parrot.
> Will Perl 6 have a tracing AP
# New Ticket Created by jerry gay
# Please include the string: [perl #35393]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35393 >
the new *_config$(O) files are not cleaned up during make
clean/realclean... until now. 's
On Monday 09 May 2005 07:53, Patrick R. Michaud wrote:
> The attached patch file adjusts C to always return false
> for offsets beyond the end of the string, and updates
> t/op/string_cclass.t to test this.
Thanks, applied!
find_cclass and find_not_cclass are in now.
jens
Leopold Toetsch wrote:
Nick Glencross <[EMAIL PROTECTED]> wrote:
Still some way off the OS md5sum, which is typically 0.15 seconds, about
12x quicker. That may sound quite a bit, but much of it can probably be
accounted for by inefficiencies in my conversion to parrot code (a
slightly awkward rol,
In Pugs, the current logic for array submatches in split() is
to stringify each element, and return them separately in the
resulting list. To wit:
pugs> split /(..)*/, 1234567890
('', '12', '34', '56', '78', '90')
Is this sane?
Thanks,
/Autrijus/
pgpUZCdoDMPb0.pgp
Description: PGP sig
> To make a Cygwin pugs, we would need to use a Cygwin GHC.[1] To the best
> of my knowledge, nobody maintains public binaries of that; and there is
> also the somewhat scary warning of a binary GHC being "a moving target"
> since cygwin1.dll often changes in ABI-breaking ways. In short, a real
> C
> "DC" == Damian Conway <[EMAIL PROTECTED]> writes:
DC> rule mv { $lastcmd:=(mv) $:=[ ]+ $:= }
DC> rule cp { $lastcmd:=(cp) $:=[ ]+ $:= }
DC> sub lastcmd { return $lastcmd }
DC> }
DC> while shift ~~ m// {
DC> say "From: @{$}";
DC> say " To: $";
DC> }
>> since files and
On Tue, 10 May 2005, Leopold Toetsch wrote:
>Dino Morelli <[EMAIL PROTECTED]> wrote:
>
>> I modified some of the .pod files in imcc/docs/ to reflect using .pir
>> instead of .imc
>
>Thanks, applied.
>leo
Thank you, leo.
Some of these .pod files are used by the website, down in
http://www.parrot
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Guys,
> Does it seem reasonable to clean up some of the tagged versions in the depot
> which have served their purpose? I would suggest:
> Remove:
> file_move_031023
> help
> V1? (or rename to something more meaningful?)
I've no clue what these tag
Second attempt and cc'ed to other Perl lists too.
Original Message
Subject: [PROPOSAL] call syntax abstraction
Date: Tue, 03 May 2005 13:58:14 +0200
Comments welcome,
leo
=head1 TITLE
Calling convention abstraction
=head1 ABSTRACT
The current Parrot calling conventions as descr
On Mon, May 02, 2005 at 09:06:42AM -0400, Rob Kinyon wrote:
> I'm willing to do any testing needed to get and keep a Cygwin port
> happy. If this is something the group wants to pursue, I'll post my
> cygghc.
Okay, here's the Cygwin situation right now. This is a summary of
discussions with Rob an
On 5/10/05, Ingo Blechschmidt <[EMAIL PROTECTED]> wrote:
> Hi,
>
> sub foo() {
> "abc" ~~ /^(.)/; # $1 now "a"
> }
>
> sub bar() {
> "def" ~~ /^(.)/; # $1 now "d"
> foo();
> say $1;# Outputs "d"
> }
>
> bar();
>
> # Correct (I hope so)?
Yeah, they're
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #35391]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35391 >
During changes related to #34994 I did introduce 3 const cast warnings,
which are j
Hi,
sub foo() {
"abc" ~~ /^(.)/; # $1 now "a"
}
sub bar() {
"def" ~~ /^(.)/; # $1 now "d"
foo();
say $1;# Outputs "d"
}
bar();
# Correct (I hope so)?
--Ingo
--
Linux, the choice of a GNU | Row, row, row your bits, gently down t
On 5/10/05, Aaron Crane <[EMAIL PROTECTED]> wrote:
> Damian Conway writes:
> > Just as $42 is a shorthand for $/[42], so too $ is a
> > shorthand for $/.
>
> Isn't $42 a shorthand for $/[41] ?
>
> I think that having 1-based digit-variables but 0-based array indexes on
> $/ is really confusing; m
Damian Conway writes:
> Just as $42 is a shorthand for $/[42], so too $ is a
> shorthand for $/.
Isn't $42 a shorthand for $/[41] ?
I think that having 1-based digit-variables but 0-based array indexes on
$/ is really confusing; mistakes of this sort seem to confirm my view.
--
Aaron Crane
DC> rule mv { $lastcmd:=(mv) $:=[ ]+
$:= }
DC> rule cp { $lastcmd:=(cp) $:=[ ]+
$:= }
DC> sub lastcmd { return $lastcmd }
DC> }
DC> while shift ~~ m// {
DC> say "From: @{$}";
DC> say " To: $";
DC> }
since files and
Guys,
Does it seem reasonable to clean up some of the tagged versions in the depot
which have served their purpose? I would suggest:
Remove:
file_move_031023
help
V1? (or rename to something more meaningful?)
Rename:
REL_0_0_5 -> RELEASE_0_0_5
(These tags would continue to be accessible by vis
Hi,
When I am building PERL 5.6.1 on Linux 2.6 Kernel AMD 64 bit machine [i.e.
"SUSE LINUX Enterprise Server 9 (x86_64) - Kernel 2.6.5-7.97-default (1)" ],
I am getting the following errors.
lib/gol-oo...ok
lib/h2ph.ok
lib/hostname.ok
lib/io_const.ok
lib/i
François" PERRAD <[EMAIL PROTECTED]> wrote:
> Two small building problems (r8030)
> 1) On MinGW, can't execute miniparrot.exe during building
> Invoking Parrot to generate runtime/parrot/include/config.fpmc --cross your
> fingers
> ./miniparrot.exe config_lib.pasm > runtime/parrot/include/config.f
Jerry Gay <[EMAIL PROTECTED]> wrote:
> ...at least they're test fixes on win32.
> the following patch adds some documentation and tests for the @ANON
> subpragma. also, fixes some tests to pass on win32. all expected tests
> pass on win32--msvc-7.1--perl-5.8.6.
Thanks, applied.
leo
Millsa Erlas <[EMAIL PROTECTED]> wrote:
> I heard that Parrot has a JIT compiler. If I understand this correctly,
> does this mean Parrot bytecode is converted to native machine hardware
> code before execution? If so, it is a good idea.
Yes, if the platform has the necessary code at least.
> JIT
Jerry Gay <[EMAIL PROTECTED]> wrote:
> some recent changes have left dynclasses unbuildable on MSWin32 due to
> an undefined external linker error.
Thanks, applied.
leo
# New Ticket Created by FranÃois PERRAD
# Please include the string: [perl #35388]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35388 >
This transaction appears to have no content
Two small building problems (r8030)
1)
# New Ticket Created by jerry gay
# Please include the string: [perl #35386]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35386 >
...at least they're test fixes on win32.
the following patch adds some documentation and
I heard that Parrot has a JIT compiler. If I understand this correctly,
does this mean Parrot bytecode is converted to native machine hardware
code before execution? If so, it is a good idea.
JIT is great, however, will it still be possible to run the Parrot
bytecode on the interpretor?
Also,
# New Ticket Created by jerry gay
# Please include the string: [perl #35385]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35385 >
some recent changes have left dynclasses unbuildable on MSWin32 due to
an undefined extern
Dino Morelli <[EMAIL PROTECTED]> wrote:
> I modified some of the .pod files in imcc/docs/ to reflect using .pir
> instead of .imc
Thanks, applied.
leo
Jeff Horwitz <[EMAIL PROTECTED]> wrote:
> the attached patch adds a new signature for spawnw so it can take a PMC
> array of arguments rather than a single string.
Thanks, applied - this one, there was a second mail with a patch.
Please note that patches to platform code need special considerati
Nick Glencross <[EMAIL PROTECTED]> wrote:
> Still some way off the OS md5sum, which is typically 0.15 seconds, about
> 12x quicker. That may sound quite a bit, but much of it can probably be
> accounted for by inefficiencies in my conversion to parrot code (a
> slightly awkward rol, and perhaps th
Nick Glencross <[EMAIL PROTECTED]> wrote:
> this patch makes some small updates to the MD5 files.
Thanks, applied.
leo
53 matches
Mail list logo
