Leopold Toetsch wrote:
Am Samstag, 24. Februar 2007 17:05 schrieb Klaas-Jan Stol:
it seems the .pbc files are stored in the repository is that
desirable?
Yes for these files.
IMO, it would be enough to store the PIR only, and have that
compiled to PBC
If you have a
Please substitute the two files attached for the identically named files in my
previous posting in
this thread. These two test files extend the test coverage
(http://thenceforward.net/parrot/
coverage/).
t/tools/ops2cutils/04-print_c_source_top.t
t/tools/ops2cutils/05-print_c_source_bottom.t
hi,
attached a patch for languages/Pynie, adding:
* more grammar rules
* statement.t for testing statements -- kinda simple, should be extended
* keyword rule, so that id's are not recognized as identifiers
regards,
kjs
Index: languages/pynie/src/parser/Grammar.pg
hi,
most languages that can run in interactive mode have some kind of
welcome message and prompt that is printed before the user can give any
input.
For example, Python prints:
Python 2.5 (r25:51908, Sep 19 2006, 09:52:17) [MSC v.1310 32 bit
(Intel)] on win
32
Type help, copyright,
On Sun, Feb 25, 2007 at 04:39:17PM +0100, Klaas-Jan Stol wrote:
most languages that can run in interactive mode have some kind of
welcome message and prompt that is printed before the user can give any
input.
Yes, this is helpful. But also one of the things we need is a way
so that we can
Patrick R. Michaud wrote:
On Sun, Feb 25, 2007 at 04:39:17PM +0100, Klaas-Jan Stol wrote:
most languages that can run in interactive mode have some kind of
welcome message and prompt that is printed before the user can give any
input.
Yes, this is helpful. But also one of the things
This week on the Perl 6 mailing lists
E ... I'm the one who *needs* the tutorial, not the one to
write it.
That makes you a prime person to capture the questions it needs to
answer! You can't evade the Responsibility Ponies that easily.
-- chromatic, responding to
Nifty.
FYI, in tcl, the two prompts can be overridden via a user defined
procedure. See http://www.tcl.tk/man/tcl8.5/UserCmd/tclsh.htm#M11
Be nice if this was also possible with the default tool.
On Feb 25, 2007, at 11:24 AM, Klaas-Jan Stol wrote:
Patrick R. Michaud wrote:
On Sun, Feb
Will Coleda wrote:
Nifty.
FYI, in tcl, the two prompts can be overridden via a user defined
procedure. See http://www.tcl.tk/man/tcl8.5/UserCmd/tclsh.htm#M11
Be nice if this was also possible with the default tool.
yup that should be possible as long as the language can access its own
This week on the Perl 6 mailing lists
Remember that the European Perl Hackathon will be held next weekend,
from 2-4 March, 2007 in Arnhem, the Netherlands. Registration is open
until Thursday, 1 March. For more information, please look at the
hackathon website
When does the specification of perl6 come to an end? Are there criteria
or milestones which define that the perl6 specification stage is at an end?
I can see that setting a time line is not easy because the effort is
volunteer based, but what about a conceptual end?
Perhaps there could be a
On Saturday 24 February 2007 22:42, Richard Hainsworth wrote:
But while perl6 continues
its evolution, without a tangible end, few are going to dedicate time
and effort to write documentation for such as me. (eg. How out of date
are the Exegesis files?)
You could make a very similar argument
hi richard
(eg. How out of date are the Exegesis files?)
very *g* just use the synopsis *g*
herbert
(proton-ce.sf.net)
___
Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos.
Gleich testen!
On 07/02/24 12:00 +0100, Paul Cochrane wrote:
parrotbug seems to be broken on win32.
Actually, I think it's broken on all platforms.
as parrotbug (the program) father, i'd like to add that i don't have
time to work on it. (and it seems to show up)
anyone wanting to work on it or even adopt it
herbert (), Richard ():
(eg. How out of date are the Exegesis files?)
very *g* just use the synopsis *g*
Hm, it might actually be a good idea to port the code examples from
the Exegeses to current Perl6, preferably also runnable in Pugs. The
ported programs could be put under examples/ in
or include a disclaimer that they are outdated as juerd sugested,
or do both. anyway this is an issue since google finds the A and E first.
im really intrested if im with juerd the only one here seeing this as an
issue.
thanks
herbert
proton-ce.sf.net
herbert (), Richard ():
(eg. How out of
On Sun, Feb 25, 2007 at 09:42:22AM +0300, Richard Hainsworth wrote:
While perl6 remains unstable in its specification (or is perceived to be
that way) and is looking (from outside a select group?) like a unending
road, wont this act as a deterrent to those who want to help hack it
into
Richard Hainsworth writes:
When does the specification of perl6 come to an end?
At a guess: when it's implemented.
Many of the recent changes have been made by Larry in response to his
trying to write the grammer, and encountering problems.
Perhaps there could be a perl6.0 specification,
Smylers wrote:
Richard Hainsworth writes:
When does the specification of perl6 come to an end?
At a guess: when it's implemented.
Many of the recent changes have been made by Larry in response to his
trying to write the grammar, and encountering problems.
With all due respect:
Once the
On Sun, Feb 25, 2007 at 09:42:22AM +0300, Richard Hainsworth wrote:
: When does the specification of perl6 come to an end? Are there criteria
: or milestones which define that the perl6 specification stage is at an end?
It seems you are presuming a Waterfall model of development here.
We're not
What backends support packed native arrays at this point? And what's
the performance like?
Native access to packed arrays is the big thing I'm looking for before I
port a pile of source filtered Perl 5 code to Perl 6. It's a simple 3D
engine, so all of the libraries I need to work with want to
On Sun, 2007-02-25 at 12:15 -0800, Jonathan Lang wrote:
I submit that you'll have even more luck discouraging such things if
you can give a reasonable and believable timeline as to when the 6.0
spec will be ready and perl 6.1 features can start being considered.
As I mentioned in another
On Sunday 25 February 2007 12:56, Geoffrey Broadwell wrote:
As I mentioned in another thread, but didn't make clear in that email: I
don't need a finished spec. I need the *current* version of spec to
actually be mostly implemented.
The implementors want the same thing.
And if it's not
On Sun, 2007-02-25 at 13:26 -0800, chromatic wrote:
On Sunday 25 February 2007 12:56, Geoffrey Broadwell wrote:
As I mentioned in another thread, but didn't make clear in that email: I
don't need a finished spec. I need the *current* version of spec to
actually be mostly implemented.
# New Ticket Created by Eric Hanchrow
# Please include the string: [perl #41617]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=41617
Here's what I did:
$ svn co -r14402 http://svn.pugscode.org/pugs pugs
$ cd pugs
$
On Sunday 25 February 2007 13:57, Geoffrey Broadwell wrote:
I'm not trying to say that the implementors should rush either, nor am I
complaining about current status; I grok the dynamics of volunteer code.
I merely disagree with the spec is all-important crowd. I personally
have a preference
Jonathan Lang writes:
Smylers wrote:
Richard Hainsworth writes:
When does the specification of perl6 come to an end?
At a guess: when it's implemented.
Many of the recent changes have been made by Larry in response to his
trying to write the grammar, and encountering
On Sun, 2007-02-25 at 14:16 -0800, chromatic wrote:
On Sunday 25 February 2007 13:57, Geoffrey Broadwell wrote:
I'm not trying to say that the implementors should rush either, nor am I
complaining about current status; I grok the dynamics of volunteer code.
I merely disagree with the spec
On Sunday 25 February 2007 12:40, Geoffrey Broadwell wrote:
What backends support packed native arrays at this point? And what's
the performance like?
Parrot does have ManagedStruct and UnManagedStruct PMCs for mapping complex C
structures. The syntax to define them is a little grotty, but
The problem is that a Sub is not a ParrotObject, so it has nowhere to
store attributes. That's why attr_str_2_num throws Can't set
non-core object attribs: it can't safely use PMC_data unless you've
passed a ParrotObject. I've attached a patch that implements a basic
attribute storage system
Now that 0.4.9 has been released, can this be committed?
Thanks,
Alek Storm
On 2/19/07, Alek Storm [EMAIL PROTECTED] wrote:
Thanks for the head start; now I know to include a test in the future.
Here is an updated version of your patch, with various minor fixes.
On 2/17/07, Allison Randal
31 matches
Mail list logo
