On 6/23/06, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
On Fri, Jun 23, 2006 at 08:27:04AM -0700, jerry gay wrote:
> audreyt++ pointed out on #parrot that there doesn't seem to be a way
> to specify where to start finding lexicals, in support of perl's
> OUTER::. e
On 6/23/06, jerry gay <[EMAIL PROTECTED]> wrote:
indeed.
my $x = 3; { { say $OUTER::x} }# 3
of course that should be
my $x = 3; { { say $OUTER::OUTER::x} }# 3
The following message from Andy Lester has been posted to perlmonks,
use.perl, and other sites, yet somehow never made it to the p6i
mailing list. I'm making sure the regular (and irregular) list readers
don't miss out on this exciting news.
~jerry
=
I've put on my overalls and rubber gloves
, etc.) into my brain, so any
>> additional
>> examples would helpful, interesting, and fun. For me, anyway :)
>
> Jerry Gay just wrote a PGE TAP grammar:
>
> <http://svn.perl.org/parrot/trunk/examples/pge/grammars/TAP.pg>
>
> -- c
I hacked a rudimentary t
On 7/5/06, via RT David H. Adler <[EMAIL PROTECTED]> wrote:
As bugs go, not a killer, but still...
The problem tests are as follows:
not ok 329 - POD test for /Users/dha/parrot-0.4.5/src/ops/experimental.ops
# Failed test (t/doc/pod.t at line 62)
# /Users/dha/parrot-0.4.5/src/ops/experimen
On 7/6/06, David H. Adler <[EMAIL PROTECTED]> wrote:
On Thu, Jul 06, 2006 at 06:22:31AM -0700, jerry gay wrote:
> perhaps you have a modified file in your working copy?
Actually, as I see it, you have a modified file in yours. :-)
I was working from the release version, which pred
On 7/6/06, Allison Randal <[EMAIL PROTECTED]> wrote:
Chip Salzenberg wrote:
> The below patches are my guess as to how to fix PGE and TGE for the recent
> change in .namespace. (That is, C<.namespace ['']> now means what it says,
> and the HLL root is reachable by C<.namespace> w/o parameters.)
On 7/6/06, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
So here's an illustrative suggestion, which I think is a variant on one of
your also-rans, albeit one that leaves the common HLL case unmarked:
.HLL 'perl5', perl5_group
.namespace ['Foo']
$P0 = get_cur_global 'x'
On 7/6/06, via RT John J. Trammell <[EMAIL PROTECTED]> wrote:
Test now uses Parrot::Distribution module instead of mass globbing.
thanks, applied as r13196, with some slight modifications, and additions.
~jerry
On 7/7/06, João Cruz Morais <[EMAIL PROTECTED]> wrote:
Are you talking about the module that has the code to run the steps
from Configure.pl?
Parrot::Config is a module *generated* by Configure.pl, containing
parrot's configuration information in a format (perl module) that's
easy for perl scri
On 7/7/06, Kevin Tew <[EMAIL PROTECTED]> wrote:
Allison Randal wrote:
> I gave a Parrot talk at a Ruby user group meeting tonight. Someone
> mentioned that they had seen somebody on #parrot who was working on a
> new Ruby implementation based on Punie. Do you exist? And is there
> anything we can
On 7/10/06, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
On Fri, Jul 07, 2006 at 01:36:06PM -0700, Chip Salzenberg wrote:
> I'm unable to hang around Portland after Friday afternoon, I'm sorry to
> report, so Saturday hackathoning will miss me. However, I will be arriving
> a day _early_ so I'l
at the chicago hackathon, i decided to create a simple tap grammar
using perl 6 regexes. you can find the example grammar at:
http://svn.perl.org/parrot/trunk/examples/pge/grammars/TAP.pg
that spawned interest from chris dolan on creating a parser using
parrot's parser grammar engine (pge.) to
On 7/11/06, Gaal Yahas <[EMAIL PROTECTED]> wrote:
On Mon, Jul 10, 2006 at 03:55:25PM -0700, Darren Duncan wrote:
> I believe that the current Test.pm already qualifies as a baby-Perl
> implementation, as overall its functionality is quite simple, and it
> uses very little of the language (especia
On 7/11/06, Jonathan T. Rockway <[EMAIL PROTECTED]> wrote:
Ian Langworth wrote:
> I mentioned YAML with a pretense I failed to mention -- that we
> wouldn't parse the YAML. That's already been done, and there are
> plenty of parsers.
I agree with this. YAML has been done and done again, in ev
On 7/12/06, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
The perl6 compiler has a custom string type, currently called
"Perl6Str". What's the canonically correct mechanism for creating
an object of that type?
$P0 = new 'Perl6Str'
$P0 = new .Perl6Str
$P0 = new [ 'Perl6Str' ]
At dif
On 7/13/06, Jonathan Rockway <[EMAIL PROTECTED]> wrote:
> are you serious? listen to what they people here are saying - we _all_
> read the raw TAP output, all the time, and not because we're TAP
> developers interested in the underlying implementations. as users, the
> (current) raw TAP diagn
On 7/15/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Folks,
Please always verify test results, don't use the Parrot output of the test as
the expected output.
If you are implementing a new feature, write the *test first*.
Thanks,
leo
PS from r13305:
@@ -1324,7 +1324,7 @@
set P2, 300
On 7/15/06, Guest via RT <[EMAIL PROTECTED]> wrote:
Also, is Parrot::Config no more? Can you please tell me what has
replaced it?
Thanks!
Swaroop
C is generated by C. so you won't
find it in a fresh working copy. you'll see it under C, which
may mean you need to add a line like C to your code
On 7/18/06, chromatic <[EMAIL PROTECTED]> wrote:
On Tuesday 18 July 2006 02:21, Audrey Tang wrote:
> Does r13347 look better? If not, please revert both my changes.
I think it's still misleading. #13364 is probably as accurate as Parrot can
report.
and has the distinction of compiling on win
On 7/23/06, Allison Randal <[EMAIL PROTECTED]> wrote:
I've just finished a read-through of all the PDDs (which I said I'd do
by OSCON), and will check in the embedded notes I made while reading
when I can connect to svn.perl.org again (known outage, nothing to worry
about).
yay!
The next step
On 7/16/06, Guest via RT <[EMAIL PROTECTED]> wrote:
Hi,
I've attached a patch for the same.
Please review and if it looks fine, can you please apply the same to trunk?
looks good. non-languages/ files have been patched and applied as
r13505. i'll follow up with the language authors, and apply
On 7/24/06, via RT Pratik Roy <[EMAIL PROTECTED]> wrote:
I am not sure if I need perl6 to build parrot.
nope.
I am using Perl5 and I get the following problem:
user562/parrot-0.4.5>perl Configure.pl
Can't locate warnings.pm in @INC (@INC contains:
/usr/perl5/5.00503/sun4-solaris /usr/perl5/
On 7/25/06, Thomas Wittek <[EMAIL PROTECTED]> wrote:
> Bearing that in mind, would the eye-socket-burning
>
> return $foo
> IF $something;
>
> really be so bad?
Operators/reserved words should be lowercase. Period. ;)
I think that this would heavily break consistency, annoying new users.
On 7/26/06, luca regini <[EMAIL PROTECTED]> wrote:
Is it possible to rename the
../include/parrot/string.h file in something else like
../include/parrot/parrot_string.h ? I see only 2
dependencies for this file in parrot.h and register.h
so this shouldn't be a big issue. I am asking this
because
On 7/28/06, via RT David Romano <[EMAIL PROTECTED]> wrote:
# New Ticket Created by "David Romano"
# Please include the string: [perl #39997]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39997 >
I've updated the documentat
On 7/28/06, jerry gay <[EMAIL PROTECTED]> wrote:
thanks for the effort! however, i don't want to apply this patch as it
is. 're_tests' was stolen directly from perl5's test suite. the idea
is that the test data this file contains is
implementation-independent. ther
On 7/30/06, Matt Diephouse <[EMAIL PROTECTED]> wrote:
In the recent push to implement all of Tcl's [expr] command, Tcl has
come to the point where it needs to understand Inf and NaN.
After a brief discussion on IRC, it seems like PMCs are the proper way
to handle this. Specifically, three new PM
On 7/31/06, David Romano <[EMAIL PROTECTED]> wrote:
Thanks for the feedback, Jerry. I changed the re_tests to not have
TODO and SKIP in the descriptions. I also changed the documentation
for p5rx.t to say that @todo_tests and @skip_tests now contain the
test numbers along with the reason why a ce
On 7/31/06, David Romano <[EMAIL PROTECTED]> wrote:
I made another patch for 01-regex.t to move the todo and skip tests
out form regex_tests, giving the same documentation as I did for
p5rx.t. Hopefully this wasn't too soon of a change, considering:
On 7/28/06, jerry gay <[E
it's not like you to submit bug reports without useful information.
how do you quantify "doesn't like svk?"
what is the output of C?
~jerry
On 8/3/06, Allison Randal <[EMAIL PROTECTED]> wrote:
Kevin Tew wrote:
> Patrick R. Michaud via RT wrote:
>> So, if we're going to allow other languages in the transform
>> bodies, we may want a "hereis" or podly {{...}}, {{{...}}} syntax to
>> delimit the transform bodies. At the moment I'm lean
On 8/3/06, Andy Lester <[EMAIL PROTECTED]> wrote:
On Aug 3, 2006, at 1:24 PM, Chip Salzenberg wrote:
> Extern functions and variables must have names that begin with
> C.
I am way out of tuits lately. Can you please add this to cage/
todo.pod for me? Or someone?
i'm sorry, andy. can not th
On 8/3/06, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
On Thu, Aug 03, 2006 at 01:31:26PM -0700, Allison Randal via RT wrote:
> Patrick R. Michaud wrote:
> >
> > I'd like there to be an :init pragma to mark subs that are to be
> > executed anytime the file is loaded. In the case of loading from
>
On 8/9/06, Allison Randal <[EMAIL PROTECTED]> wrote:
Chip Salzenberg wrote:
>> pbc_merge doesn't allow multiple :load routines.
>
> That's a bug, Shirley.
Currently it's a feature. Only one :load routine is allowed per PIR
file, and pbc_merge basically just packs all the compiled code together.
recently, perl 6 development has taken the form of a multi-method
dispatch. that is, multiple implementations are under active
development. this includes pugs (in haskell,) v6 (in perl5,)
v6-Compiler (in perl6,) and perl6 (on parrot.) hopefully, each of
these returns the same result, a working[1]
On 8/11/06, Larry Wall <[EMAIL PROTECTED]> wrote:
Just to avoid repeating some of the discussion, here's a link to #perl6:
http://colabti.de/irclogger/irclogger_log/perl6?date=2006-08-07,Mon&sel=110#l193
The discussion goes on and off for most of the rest of the page,
so you probably want
[dropped perl-qa and p6l from this thread, as it's repo-related, and not
directly related to those lists]
On 8/12/06, Audrey Tang <[EMAIL PROTECTED]> wrote:
在 2006/8/12 上午 3:01 時,jerry gay 寫到:
> for "managed," i have a few ideas. currently, the suite lives in the
>
[parrot-porters and p6l have been removed from this thread, as discussion of
testing tools is not directly related to those lists]
On 8/11/06, Agent Zhang <[EMAIL PROTECTED]> wrote:
On 8/12/06, jerry gay <[EMAIL PROTECTED]> wrote:
this last testing rule i mentioned beco
On 8/14/06, chromatic <[EMAIL PROTECTED]> wrote:
Ugh, so this means editing the canonical test repository for every
status-changing update to every implementation? Yuck. This seems like a
problem for implementation-specific harnesses and reporting tools.
this is what prompted me to start th
On 8/15/06, chromatic <[EMAIL PROTECTED]> wrote:
Here's a proposed patch that seems to work okay for me on Linux. It's not
great or beautiful, mostly because of the Makefile hackery. It's a starting
point though. I suspect Windows might complain.
i'll happily test, but i can't apply it, as i
On 8/16/06, chromatic <[EMAIL PROTECTED]> wrote:
On Wednesday 16 August 2006 08:57, jerry gay wrote:
> i'll happily test, but i can't apply it, as it seems not to be in the
> format my patch util expects. did you use C? i don't see the
> familiar "Index: &
On 8/15/06, chromatic <[EMAIL PROTECTED]> wrote:
Here's a proposed patch that seems to work okay for me on Linux. It's not
great or beautiful, mostly because of the Makefile hackery. It's a starting
point though. I suspect Windows might complain.
windows indeed complains. not only about miss
On 8/17/06, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
How about a 'default' opcode that provides a value instead of null? It
would work for strings and PMCs. Something like:
$S0 = default hsh['key'], ''
or
$P0 = new .Undef
...
$P1 = default hsh['key1'], $P0
$P1 = d
On 8/17/06, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
There might be a cognitive dissonance here with "err", since
C in pasm/pir is testing for null, while C in
perl6 tests for definedness. While it doesn't much matter
for strings in the examples above, it might make a difference for
$
On 8/21/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
My preference: soft limit 80 - keep lines shorter, if it's easy
hard limit ~100 - you SHALL not exceed it
coding standards are quite helpful, but cannot be applied absolutely.
there are good reasons why a line of code might
On 8/25/06, Will Coleda <[EMAIL PROTECTED]> wrote:
What about 'say'? It's a method, not an opcode, and:
say $S0
works just fine.
but C does *not* work.
i find that annoying.
either make the syntax for methods different than ops (eg C<$S0.say()>)
or make C an opcode,
or dodge the syntax issue
On 8/25/06, Trey Harris <[EMAIL PROTECTED]> wrote:
In a message dated Fri, 25 Aug 2006, Mark J. Reed writes:
> I think the justification for Luke's POV is the number of operations
> each class provides. But my perspective agrees with Juerd -
> subclasses can remove functionality as well as addi
On 8/31/06, Luke Palmer <[EMAIL PROTECTED]> wrote:
On 8/31/06, Juerd <[EMAIL PROTECTED]> wrote:
> Still, though, How would you specify :g? It doesn't make a lot of sense
> on rx// -- just like you can't use it with qr// in Perl 5.
It is a good point that it doesn't belong on the regex. Perhaps:
On 9/1/06, Trey Harris <[EMAIL PROTECTED]> wrote:
In a message dated Fri, 1 Sep 2006, Paul Seamons writes:
> I'm not sure if I have seen this requested or discussed.
This was definitively rejected by Larry in 2002:
http://www.nntp.perl.org/group/perl.perl6.language/9343
He has not revisited t
On 9/2/06, Alberto Simões <[EMAIL PROTECTED]> wrote:
Alberto Simões wrote:
> Hi
>
> I created a ticket in RT two days ago (well, one day ago) and still
> waiting for it to be created, so, forget RT and here it goes.
One more day, and no ticket yet. I wonder what is happening.
i've forwarded a
On 9/5/06, via RT Will Coleda <[EMAIL PROTECTED]> wrote:
From the recently updated pdd07:
C source files, and files largely consisting of C (e.g. yacc, lex,
PMC, and opcode source files), must end with this block:
/*
* Local variables:
* c-file-style: "parrot"
* End:
* vim: expandtab
On 9/19/06, via RT Paul Cochrane <[EMAIL PROTECTED]> wrote:
# New Ticket Created by "Paul Cochrane"
# Please include the string: [perl #40361]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=40361 >
This is a patch of more Pe
On 9/19/06, Paul Cochrane <[EMAIL PROTECTED]> wrote:
> firstly, line endings are unrelated to this effort and should be a
> separate patch. that's no biggie, and alone wouldn't stop me from
> applying.
I can do that in a separate patch if you want. That's not a major
problem, and probably a good
On 9/19/06, Paul Cochrane <[EMAIL PROTECTED]> wrote:
This is going to sound rather silly, but... how does one enter a new
ticket to RT? I've got an account, but can't see anywhere on
rt.perl.org where one can add a new ticket. There's also no help link
I can go to to work out what to do. Shou
On 9/19/06, Paul Cochrane <[EMAIL PROTECTED]> wrote:
Jerry,
> all new rt tickets are created via parrotbug. it may not be sexy, but
> it's what we've got :-)
I'm not 100% sure if it worked, as parrotbug gave this warning:
Use of uninitialized value in concatenation (.) or string at
./parrotbug
http://www.parrotcode.org/misc/parrotsketch-logs/irclog.parrotsketch-200609/irclog.parrotsketch.20060918
or, for the browser- or email-client- newline-challenged:
http://xrl.us/rs3n
enjoy.
~jerry
On 9/20/06, Fagyal Csongor <[EMAIL PROTECTED]> wrote:
I was wondering if there is (or there should be) a documentation on how
to elegantly write Perl6 code.
yes, there should be.
I am afraid that when I will be starting to write Perl6 code, it will be
too much Perl5-ish, and I will end up rew
On 9/19/06, via RT Paul Cochrane <[EMAIL PROTECTED]> wrote:
# http://rt.perl.org/rt3/Ticket/Display.html?id=40364 >
This patch changes the line endings of the files listed below from dos to unix.
thanks, applied by bernhard, r14667.
~jerry
On 9/20/06, chromatic <[EMAIL PROTECTED]> wrote:
On Wednesday 20 September 2006 09:53, Jerry Gay via RT wrote:
> thanks, applied as r14673, with a minor fix:
>
> -$print_coda();
> +&print_coda();
I wouldn't mind seeing the '&' go away entirely. It'
On 9/21/06, via RT Paul Cochrane <[EMAIL PROTECTED]> wrote:
This patch gets code_coda.t to test for multiply-defined codas (for
those cases when a file append or automated tool adds a coda
unnecessarily). I have a feeling it's not pretty code, but my perl
foo is only slowly improving.
great id
On 9/25/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Hi folks,
Read the journal
http://pugs.blogs.com/pugs/2006/09/check_smoke_res.html
Follow the link:
http://m19s28.vlinux.de/cgi-bin/pugs-smokeserv.pl?
Click at a recent entry with a SYN link
Then click on "02 Syntax"
Then on e.g.:
- Show
On 10/2/06, Jonathan Lang <[EMAIL PROTECTED]> wrote:
I'm not used to programming styles where a programmer intentionally
and explicitly forbids the use of otherwise perfectly legal code. Is
there really a market for this sort of thing?
use strict;
On 10/2/06, Aaron Sherman <[EMAIL PROTECTED]> wrote:
Jonathan Lang wrote:
> I'm not used to programming styles where a programmer intentionally
> and explicitly forbids the use of otherwise perfectly legal code. Is
> there really a market for this sort of thing?
>
use strict;
you're so twel
On 10/9/06, Karl Forner <[EMAIL PROTECTED]> wrote:
Hi,
It's not that easy to contribute to parrot development.
I got into that by picking a TODO task about *BooleanArrays, that seemed
appropriate for a Parrot newbie that
knows a bit about algorithmics and Data structures.
thank you for your en
On 10/9/06, Paul Cochrane <[EMAIL PROTECTED]> wrote:
Hi all,
In r14862, Configure.pl throws an error when processing the Manifest.
The error is:
Checking MANIFEST...No such file: ext/Parrot-Embed/Embed.xs
Ack, some files were missing! I can't continue running
without everything here. Please
On 10/11/06, via RT Paul Cochrane <[EMAIL PROTECTED]> wrote:
# http://rt.perl.org/rt3/Ticket/Display.html?id=40503 >
This patch removes the paragraph in DEPRECATED.pod mentioning that the
.imc file extension is deprecated since there are no longer any .imc
files in Parrot (having all been turned
On 10/11/06, Jonathan Worthington <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
> What's a "C++ comment"? If you mean //...\n comments, those are legal
> in ANSI-99 C
Parrot is using ANSI-98 C, I believe. And //\N+\n comments are not legal
in that.
jonathan ment C89 of course. some compi
On 10/11/06, Paul Cochrane <[EMAIL PROTECTED]> wrote:
> i'm not 100% sure this is the right thing to do, either. the most
> recent version of "perl 6 and parrot essentials" still makes reference
> to '.imc' files. with this paragraph in deprecated.pod, there's
> something to grep for that might h
On 10/11/06, Bernhard Schmalhofer via RT
<[EMAIL PROTECTED]> wrote:
On Mi. 11. Okt. 2006, 08:10:45, [EMAIL PROTECTED] wrote:
> Yes, I got exacly the same output from r14895. Actually, this patch
> was already applied by Bernhard in r14870, which explains why the
> effected files list looks dif
On 10/16/06, chromatic <[EMAIL PROTECTED]> wrote:
On Monday 16 October 2006 02:00, Paul Cochrane wrote:
> This patch adds a test to the coding standards which checks for space
> or tab characters after a curly brace when the curly is the last
> printable character on the line. The pumpking hasn
On 10/16/06, jerry gay <[EMAIL PROTECTED]> wrote:
i see no reason to keep this specific to curlies.
i hate all useless trailing whitespace equally :)
for vim users, these settings may help find trailing spaces and leading tabs:
set list
set listchars=trail:-,tab:\.\
note in this cas
looks like a valid problem, and a valid solution... commit away!
~jerry
On 10/17/06, Kevin Tew <[EMAIL PROTECTED]> wrote:
Used Cwd::abs_path like FindBin in perl 5.8.6 does.
defaults.pm |3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
Index: config/init/defaults.pm
=
On 10/17/06, Andy Lester <[EMAIL PROTECTED]> wrote:
On Oct 17, 2006, at 3:33 PM, Kevin Tew wrote:
>if (!info->thaw_result) info->thaw_result = pmc;
>else *info->thaw_ptr = pmc;
No, definitely not.
if ( foo ) {
bar();
}
else {
bat();
}
if
On 10/24/06, Will Coleda <[EMAIL PROTECTED]> wrote:
Not all tests follow the "one test reporting on many files" paradigm:
see t/codingstd/perlcritic.t
FWIW,in general, I prefer the perlcritic method.
as i just wrote in a new ticket for perl coding standard test reformatting...
coding standard
On 10/25/06, Chris Dolan <[EMAIL PROTECTED]> wrote:
On Oct 25, 2006, at 1:24 PM, Jerry Gay (via RT) wrote:
> modify perl coding standard test format to match the c tests--one test
> per standard, rather than one test per file.
>
> coding standard tests are designed to test ma
On 11/7/06, Paul Cochrane <[EMAIL PROTECTED]> wrote:
Thanks Bernhard! Added to the list.
Paul
> When the commit is associated with a ticket in RT, I usually copy&paste the
> ticket header. e.g.
>
> #39197: [CAGE] lib/Parrot/Test.pm ignores core dumps failures!CU,
>
> Bernhard
paul~
i to
On 11/13/06, SADAHIRO Tomoyuki <[EMAIL PROTECTED]> wrote:
On Sat, 11 Nov 2006 16:34:55 -0800, Chip Salzenberg (via RT) wrote
> because the Perl sprintf test suite seems to think that the right value
> for sprintf('%e',1) is "1e+00", but Win32 seems to return "1e+000" (note
> the extra digit in t
On 12/10/06, James E Keenan <[EMAIL PROTECTED]> wrote:
James E Keenan wrote:
And now here's what I got with
perl Configure.pl (i.e., no options)
vi Makefile (to eliminate -bundle from LD_LOAD_FLAGS)
make
Failure at this point has now become frequently observed.
[parrot] 631 $ perl Configure
On 12/12/06, Ovid <[EMAIL PROTECTED]> wrote:
Hi all,
A couple of quick things.
First, how do I do introspection in Pugs? CPAN's Perl6::Bible hasn't
been updated in a while, but the various ways to get a list of methods
(from
http://search.cpan.org/dist/Perl6-Bible/lib/Perl6/Bible/S12.pod#Intro
On 12/16/06, [EMAIL PROTECTED] via RT <[EMAIL PROTECTED]> wrote:
On Sat Nov 11 11:53:27 2006, [EMAIL PROTECTED] wrote:
> Not sure if this is a bug or not, but I noticed that the open opcode
> creates its argument if the desired file doesn't exist.
>
There are two variants of the open opcode: this
On 12/20/06, Jonathan Worthington <[EMAIL PROTECTED]> wrote:
Leopold Toetsch wrote:
> Am Mittwoch, 20. Dezember 2006 05:59 schrieb Will Coleda:
>
>> Are Hash and Array supposed to have different results on unset keys?
>>
>
> The .Undefs returned by Arrays are IMHO and unfortunate leftover of he e
On 12/31/06, via RT Lee Duhem <[EMAIL PROTECTED]> wrote:
# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41158]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41158 >
The here docs in test C cause t/
On 12/30/06, James Keenan <[EMAIL PROTECTED]> wrote:
Following a suggestion made earlier today by Coke, I am submitting
this file for t/tools/pmc2utils/.
thanks, applied as r16409.
~jerry
On 1/7/07, via RT Bernhard Schmalhofer
<[EMAIL PROTECTED]> wrote:
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #41198]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41198 >
Hi,
the files
On 1/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
+Matching against a C object will call the C method
+defined in the grammar. The C method may either be a rule
+itself, or may call the actual top rule automatically. How the
+C determines the top rule is up to the grammar, but normal
+Per
On 1/8/07, Paul Cochrane via RT <[EMAIL PROTECTED]> wrote:
On Thu Nov 16 05:00:35 2006, coke wrote:
> Any files that are copied from somewhere else should be immune from
> our coding standards.
>
> This includes items in
>
> lib/Parse/RecDescent.pm, which is from CPAN, or
>
> languages/tcl/librar
Fellow birders~
On Saturday, 13 January, 2007, please join us on IRC in #parrot
(irc.perl.org) to work on closing out as many RT
(https://rt.perl.org/rt3/) tickets as possible in the parrot queue.
This will help us get ready for the next release of parrot 0.4.8,
scheduled for Tuesday 16 January 2
On 1/13/07, Matt Diephouse <[EMAIL PROTECTED]> wrote:
Ah, I see what happened here. I had to change things around in the first
place to be able to link in another object file with my dynamic opcodes. I
ended up changing dynoplibs.pl to link arguments differently if they were
object files. But my
On 1/12/07, James Keenan <[EMAIL PROTECTED]> wrote:
Following my refactoring of tools/build/pmc2c.pl, particle asked me
to look at phalanxing a couple of the other build tools: ops2pm.pl
and ops2c.pl. Since ops2pm.pl is invoked at the very beginning of
the 'make' process, I decided to focus th
On behalf of the Parrot team, I'm proud to announce Parrot 0.4.8,
"Eponymous." Parrot (http://parrotcode.org) is a virtual machine aimed
at running all dynamic languages.
You may now grab Parrot 0.4.8 from the CPAN.
Parrot 0.4.8 News:
- Compilers:
+ HLLCompiler: added tracing options, modified
i never officially closed the repo to commits, but for those of you
awaiting parrot's release, it's now complete. you may commit freely.
thanks for your patience.
~jerry
On 1/19/07, chromatic <[EMAIL PROTECTED]> wrote:
On Friday 19 January 2007 04:46, Paul Cochrane wrote:
> I wanted to commit a
> line endings change to shootout.t in lua, but when I went 'svk push' I
> got an "Empty commit message" error again and the only way I know to
> fix this is to use 'svk
On 1/19/07, Allison Randal <[EMAIL PROTECTED]> wrote:
(That also means you can monkey around with the args before passing them
on to the wrapped sub.)
- It should be possible both to put multiple wrappers/traces on a
subroutine, and to put wrappers around other wrappers. So these are all
possib
On 1/24/07, Jeffrey Thalhammer via RT <[EMAIL PROTECTED]> wrote:
Perl-Critic-1.01 is on its way to a CPAN mirror near you. I ran all
the way through codingstd/perlcritic.t on my wimpy Win32 machine, and
memory utilization was stable during the entire run when using Perl-
Critic-1.01. Let me kno
i spent some time with PDD22 this week. i've started writing tests for
the ParrotIO object, which you'll find in the attached patch. you'll
also find some notes i've made both in the test file, and in the spec.
i find writing spec-based tests to be extremely enlightening. the act
of writing code
On 1/26/07, Klaas-Jan Stol <[EMAIL PROTECTED]> wrote:
attached is a patch including the PIR language using PGE.
My earlier patch was not (yet) delivered, so I'm sending the zip'ed
version, which is much smaller.
great! this has been applied (with changes to make it cross-platform
friendly) as
On 1/31/07, Allison Randal <[EMAIL PROTECTED]> wrote:
Answering some questions from PDD 22.
thanks! all your edits are sane.
- On naming, let's go with a simple 'IO'. It's in the parrot namespace,
so ['parrot';'IO']. IO is the base class, and may have other children
such as ['parrot'; 'IO'; '
On 2/7/07, chromatic <[EMAIL PROTECTED]> wrote:
On Wednesday 07 February 2007 12:25, Klaas-Jan Stol wrote:
> absolutely true. I'm not sure; is pod2html present on any platform where
> perl is? If so, then it can be incorporated into step.pm, (that makes
> the Makefiles), so it can done when runn
On 2/11/07, via RT Paul Cochrane <[EMAIL PROTECTED]> wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #41485]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41485 >
chromatic asked me recently
101 - 200 of 608 matches
Mail list logo