On Mon, Nov 24, 2008 at 2:00 AM, Patrick R. Michaud [EMAIL PROTECTED]wrote:
On Mon, Nov 24, 2008 at 02:31:58AM +0100, Jonathan Worthington wrote:
Oh, argh, so .line now carries the file *and* the line number?.I wanted
it to just carry the line number (the clue's in the name... ;-)) and
On Sun, Nov 23, 2008 at 10:08 PM, Jonathan Worthington
[EMAIL PROTECTED]wrote:
Klaas-Jan Stol via RT wrote:
On Thu Dec 13 04:35:13 2007, pmichaud wrote:
On Sat Sep 29 08:57:28 2007, kjs wrote:
A few months ago, the #line directive was implemented.
I'm wondering what the reason was why
I'm not entirely sure whether it was *just* a rename... ISTR there was also
something to do with a look-up of names. Pm knows more about it :-)
(admittedly, the topic is not well-defined then.)
kjs
On Thu, Nov 20, 2008 at 4:21 PM, Will Coleda via RT
[EMAIL PROTECTED] wrote:
On Sun Nov 16
On Sat, Nov 8, 2008 at 9:22 PM, chromatic [EMAIL PROTECTED] wrote:
On Wednesday 05 November 2008 14:31:21 [EMAIL PROTECTED] wrote:
Modified:
trunk/compilers/pirc/new/pir.l
trunk/compilers/pirc/new/pirlexer.c
trunk/compilers/pirc/new/pirlexer.h
Log:
[pirc] add support for
I'd say kill it, and if we ever want to introduce new pragmas into PIR, we
reintroduce. This way, .pragma keyword is not recognized without a reason.
(recently I've become a great fan of being able to override commandline
options with directives in the file processed; .pragma directive would be
fixed in r32209.
The warning of inconsistent dll linkage no longer occurs on microsoft
visual studio, which resolves this issue.
kjs
I think the issue of inconsistent dll linkage has been resolved recently
by adding the YYMALLOC and YYFREE #defines to imcc source.
Can other windows people confirm this? Then this ticket can be closed.
Thank you very much,
kjs
On Mon, Oct 20, 2008 at 6:18 PM, chromatic [EMAIL PROTECTED] wrote:
On Sunday 19 October 2008 14:02:58 Klaas-Jan Stol wrote:
when running code as this:
.sub main :immediate
load_bytecode foo.pir
.end
(assuming you have a file 'foo.pir'), IMCC can't handle this.
This is because
PDD19 already states that there's no limit, and the note that in the
future such a limit might be introduced is also there.
So, issue is resolved.
kjs
I think this ticket has been resolved by the decision that method names
must be quoted (as stated in pdd19).
I propose to close ticket.
kjs
On Thu Oct 04 16:39:31 2007, coke wrote:
On Sep 29, 2007, at 12:07 PM, Klaas-Jan Stol (via RT) wrote:
# New Ticket Created by Klaas-Jan Stol
fixed in r31956
On Mon, Oct 13, 2008 at 2:10 AM, Andrew Whitworth [EMAIL PROTECTED]wrote:
On Sun, Oct 12, 2008 at 9:27 AM, via RT Klaas-Jan Stol
[EMAIL PROTECTED] wrote:
currently, the .line directive takes both an integer (for line number)
and a
string (for filename) argument.
I propose to split
On Fri, Oct 3, 2008 at 2:23 PM, I Sop [EMAIL PROTECTED] wrote:
From: Patrick R. Michaud via RT [EMAIL PROTECTED]
Subject: Re: [perl #59576] [PATCH] 'property' scope for PAST::Var
To: [EMAIL PROTECTED]
Date: Friday, October 3, 2008, 12:31 PM
On Thu, Oct 02, 2008 at 02:16:01PM -0700, I
sorry, documentation and source should be reorganized at some point. For
now, please check out compilers/pirc/README.pod.
sorry for the confusion,
kjs
On Tue, Sep 9, 2008 at 5:31 PM, NotFound [EMAIL PROTECTED] wrote:
I put the commands that I'm using in the README file (but that's for MSVC
on
On Sat, Aug 30, 2008 at 10:40 AM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol wrote:
On Sat, Aug 30, 2008 at 11:04 AM, Allison Randal [EMAIL PROTECTED]
wrote:
Yes, it will be deprecated, or at least renamed. The C.return
directive
without parentheses is an old convention
It seems that the error condition refers to the case where too many
arguments are passed (#args #params).It's not really overflow in that
sense, IMHO, just too many arguments passed.
I think an exception is already thrown when that happens, not sure.
kjs
On Tue, Sep 9, 2008 at 12:02 AM,
hi,
recently I had a good look at Parrot's Makefile to figure out what link
flags I need to link PIRC against libparrot.
This worked out quite well, and I'm now able to link in libparrot so PIRC
can now call all Parrot functions.
(the only major thing that needs to be done to get rid of IMCC is
On Tue, Sep 2, 2008 at 12:43 PM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol wrote:
This must make the following syntax rule illegal:
target = null
because if null is declared as a .local, you can't know whether you want
to nullify target, or want to set target's value
On Fri, Sep 5, 2008 at 1:28 PM, Will Coleda [EMAIL PROTECTED] wrote:
On Fri, Sep 5, 2008 at 3:45 AM, Christoph Otto via RT
[EMAIL PROTECTED] wrote:
On Fri Jun 27 13:14:53 2008, coke wrote:
While I think this particular example is now valid with the new calling
conventions, you can get a
I checked in some major changes that allow all keywords (types and if, null,
etc.) as identifiers. Cleanup and maybe a refactor will follow later.
kjs
On Wed, Sep 3, 2008 at 10:35 AM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol wrote:
On Tue, Sep 2, 2008 at 2:28 PM, Allison Randal
On Tue, Sep 2, 2008 at 8:08 AM, François Perrad [EMAIL PROTECTED]wrote:
It seems that PIR uses only one name space of identifiers.
$ cat const.pir
.const int cst = 42
.sub 'cst'
print cst
.end
$ parrot const.pir
error:imcc:undefined identifier 'cst'
in file 'const.pir' line
On Tue, Sep 2, 2008 at 12:43 PM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol wrote:
This must make the following syntax rule illegal:
target = null
because if null is declared as a .local, you can't know whether you want
to nullify target, or want to set target's value
On Tue, Sep 2, 2008 at 2:28 PM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol wrote:
So, preferably, the special words in PIR will be allowed as identifiers
('if','unless', 'null') and PIR will DWIM. What about the type
identifiers:
int, num, pmc, string; should these be allowed
On Sat, Aug 30, 2008 at 11:04 AM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol (via RT) wrote:
The parentheses surrounding the arguments are mandatory. Besides making
sequence break more conspicuous, this is necessary to distinguish this
syntax from other uses of the C.return
On Sat, Aug 30, 2008 at 12:27 PM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol wrote:
This is another one of those muddy cases in PIR where words conflict
when
they shouldn't. I can't think of any way that it's actually useful to
have a
variable named 'add' prevent you from
On Thu, Aug 28, 2008 at 10:07 PM, Allison Randal [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Opcode names are not reserved words in PIR, and may be used as variable
names.
For example, you can define a local variable named Cprint. [See RT
#24251]
+Note that by using an opcode name
On Fri, Aug 29, 2008 at 11:06 AM, Klaas-Jan Stol [EMAIL PROTECTED]wrote:
On Thu, Aug 28, 2008 at 10:07 PM, Allison Randal [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Opcode names are not reserved words in PIR, and may be used as variable
names.
For example, you can define a local
docs/imcc/macros.pod was integrated into pdd19 some time ago. That's all
information available on macros, currently
kjs
On Mon, Aug 25, 2008 at 10:08 AM, Reini Urban [EMAIL PROTECTED] wrote:
pdd19_pir.pod references the not-existing docs/imcc/macros.pod.
It would be nice if this documents
On Mon, Aug 18, 2008 at 10:31 PM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol wrote:
On Sat, Aug 16, 2008 at 9:41 AM, Allison Randal [EMAIL PROTECTED]mailto:
[EMAIL PROTECTED] wrote:
Klaas-Jan Stol wrote:
On Wed Aug 06 05:53:07 2008, kjs wrote:
My
On Sat, Aug 16, 2008 at 9:41 AM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol wrote:
On Wed Aug 06 05:53:07 2008, kjs wrote:
My proposal would be to change the concatenate dot into .., which looks
like it, but is more explicit, and will prevent such mistakes.
I agree
fixed in r30252.
What's the general feeling about this proposal?
Any thoughts of the architect?
thanks,
kjs
On Thu, Aug 7, 2008 at 5:17 PM, Bob Rogers [EMAIL PROTECTED]wrote:
From: Andrew Whitworth [EMAIL PROTECTED]
Date: Thu, 7 Aug 2008 11:36:16 -0400
On Thu, Aug 7, 2008 at 11:18 AM, Bob Rogers
On Fri, Aug 8, 2008 at 12:57 PM, Patrick R. Michaud [EMAIL PROTECTED]wrote:
On Thu, Aug 07, 2008 at 10:15:24AM -0400, Will Coleda wrote:
Now, if the problem is that the register allocator is broken, then
let's fix the register allocator. If :unique_reg is just a workaround
because fixing
fixed in r30169.
apologies for messing up.
On Wed, Aug 6, 2008 at 8:30 PM, Jonathan Worthington [EMAIL PROTECTED]wrote:
Will Coleda wrote:
Can you describe a situation where this occurs that isn't a bug in the
register allocator?
Yes. IIRC, it was added when I was working on the .Net bytecode translator,
and it needed to take
[this message was not sent to list, which it seems it should have; hence the
forward.]
-- Forwarded message --
From: Andrew Whitworth via RT [EMAIL PROTECTED]
Date: Thu, Aug 7, 2008 at 12:11 AM
Subject: [perl #57656] [PROPOSAL][PIR] change PIR sugar for concat into ..
(or
On Thu, Aug 7, 2008 at 12:45 PM, Will Coleda [EMAIL PROTECTED] wrote:
On Wed, Aug 6, 2008 at 3:30 PM, Jonathan Worthington [EMAIL PROTECTED]
wrote:
Will Coleda wrote:
Can you describe a situation where this occurs that isn't a bug in the
register allocator?
Yes. IIRC, it was added
On Thu, Aug 7, 2008 at 1:33 PM, Jonathan Worthington [EMAIL PROTECTED]wrote:
Will Coleda wrote:
So, again, do we in parrot want to support the ability to dig into our
callers register set and pull out a particular register since we have
no way to say which register that is when we're using
, Jul 31, 2008 at 10:07:49AM +0100, Klaas-Jan Stol wrote:
On Wed, Jul 30, 2008 at 9:06 PM, via RT Will Coleda wrote
From PDD19:
=item .pragma n_operators [deprecated]
does this mean that by default all ops will have the n_ prefix by
default?
That would imply some variants of these ops
On Wed, Jul 30, 2008 at 8:22 PM, Will Coleda via RT
[EMAIL PROTECTED] wrote:
On Wed, Jul 30, 2008 at 9:13 AM, via RT Klaas-Jan Stol
[EMAIL PROTECTED] wrote:
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #57410]
# in the subject line of all future
On Wed, Jul 30, 2008 at 9:06 PM, via RT Will Coleda
[EMAIL PROTECTED] wrote:
# New Ticket Created by Will Coleda
# Please include the string: [perl #57438]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=57438
Implemented in r29908.
kjs
On Wed, Jul 30, 2008 at 7:51 PM, via RT Will Coleda
[EMAIL PROTECTED] wrote:
# New Ticket Created by Will Coleda
# Please include the string: [perl #57430]
# in the subject line of all future correspondence about this issue.
# URL:
Attached is a patch that does this, but I'm not quite sure about the last 2
statements.
Hence, this is submitted as a patch instead of me applying it myself.
kjs
On Wed, Jul 30, 2008 at 7:47 PM, via RT Will Coleda
[EMAIL PROTECTED] wrote:
# New Ticket Created by Will Coleda
# Please
a Brainf*** interpreter in lolcode:
http://forum.lolcode.com/viewtopic.php?id=51
I wonder whether it runs on parrot :-)
kjs
without any internet connection at home you get really bored.
that means, time for some fun :-)
Included is a patch that implements JSON with the PCT. As JSON is just a
data description (sub) language, I was not sure what the TOP rule should
contain;
I decided for now that it would be just value*
maybe I overlooked something, but wouldn't specifying the full outer subname
(including its namespace) help?
like so:
.namespace ['B']
.sub 'inner' :outer(['A';'outer'])
...
.end
instead of the proposed :lexid property.
just a thought. maybe there's something i'm overlooking or missing, but to
hi,
as far as I know, languages/abc is an implementation of the 'basic
calculator', commonly found on unix platforms, known as 'bc'.
For some reasons, this name changed to 'abc' some time ago.
However, there is also a programming language called 'abc' (a precursor of
Python, Guido van Rossum
On Thu, Jun 12, 2008 at 3:18 PM, Francois PERRAD via RT
[EMAIL PROTECTED] wrote:
Klaas-Jan Stol (via RT) a écrit :
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #55670]
# in the subject line of all future correspondence about this issue.
# URL: http
I came accross this:
http://www.cs.iastate.edu/~design/vmil/cfp.shtml
I didn't read the whole page, but this caught my eye:
I had to think about modularization with the whole compiler
architecture on Parrot (PCT).
quote
Research and experience papers: These submissions should describe work
that
somehow a fresh checkout has resolved the problem
(but my other sandbox was still up to date according to svn status...)
anyhow, this ticket can be rejected.
kjs
On Thu, Jun 5, 2008 at 10:38 AM, via RT Klaas-Jan Stol
[EMAIL PROTECTED] wrote:
# New Ticket Created by Klaas-Jan Stol
# Please
On 5/28/08, Will Coleda [EMAIL PROTECTED] wrote:
Would it be helpful to have comments that are posted on articles on
parrotblog sent to this mailing list?
Very helpful IMO.
kjs
Hi,
I'm converting the tutorial on the PCT to POD files, so they can be
added to languages/squaak/doc.
I do have a question on the license; not sure if this is an issue. I
put the tutorial in the public domain, by adding a section 'license'
below each episode, like so:
The source code in this
On Fri, May 23, 2008 at 4:05 AM, Will Coleda via RT
[EMAIL PROTECTED] wrote:
On Wed Oct 17 12:09:54 2007, bernhard wrote:
Currently following PIR is failing because of the '#' in the '.param' list.
.sub main :main
( $S1 ) = my_sub( 'hello', 'world' )
say $S1
.end
.sub my_sub
On Fri, May 23, 2008 at 2:42 PM, Andrew Whitworth [EMAIL PROTECTED] wrote:
On Fri, May 23, 2008 at 6:55 AM, Klaas-Jan Stol [EMAIL PROTECTED] wrote:
IIRC, the blank line stuff in .param lines has to do with the
helper_state non-terminal; this is a kludge to make things work
currently
Hi,
I'm converting the tutorial on the PCT to POD files, so they can be
added to languages/squaak/doc.
I do have a question on the license; not sure if this is an issue. I
put the tutorial in the public domain, by adding a section 'license'
below each episode, like so:
The source code in this
On Thu Dec 13 05:54:17 2007, kjs wrote:
On Tue Jun 14 02:30:00 2005, chip wrote:
It makes sense to allow e.g. C$P0 = add $P1, $P2 as alternative
syntax for Cadd $P0, $P1, $P2. However, when the first parameter is
inout rather than out, assignment syntax is *not* appropriate.
For
amber sources are no longer stored in the parrot repository.
ticket rejected.
amber sources are no longer stored in the parrot repository.
ticket rejected.
amber sources are no longer stored in the parrot repository.
ticket rejected.
amber sources are no longer stored in the parrot repository.
ticket rejected.
amber sources are no longer stored in the parrot repository.
ticket rejected.
amber sources are no longer stored in the parrot repository.
ticket rejected.
hi,
it seems that there is overlap in the strings pdd (28) and the strings
implementation document in docs/strings.pod.
I'm not sure if this is a good idea; I think these should be merged.
If so, I'll open a ticket to do so (but wanted to check first)
kjs
On Mon, Apr 28, 2008 at 1:53 PM, Allison Randal [EMAIL PROTECTED] wrote:
Bob Rogers wrote:
From: Klaas-Jan Stol [EMAIL PROTECTED]
about the removal of internal_exception: the specified ticket (in the
list on the wiki) does not have a conclusion: no final decision seems
Hi,
Could anybody check out ticket #39845?
I replied on it multiple times, but somehow the reply button is not
visible anymore when I log in.
I think the ticket can be closed.
thanks heaps,
kjs
On Sun, Apr 27, 2008 at 2:00 PM, Allison Randal [EMAIL PROTECTED] wrote:
By popular demand, I've put my ongoing list of tasks for the concurrency
implementation branch on the wiki. Mark a task you start to work on with
your initials, so we know you're working on it:
On Sun, Apr 27, 2008 at 7:38 PM, Mark Glines [EMAIL PROTECTED] wrote:
On Sun, 27 Apr 2008 19:25:55 +0100
Klaas-Jan Stol [EMAIL PROTECTED] wrote:
Hi,
Could anybody check out ticket #39845?
I replied on it multiple times, but somehow the reply button is not
visible anymore when I
hi,
there are some RT tickets for languages/amber, but this language does
not seem to be in the repository anymore.
I'd say the tickets can be rejected. Am I right?
48180
48182
48184
48186
48188
48192
kjs
On Sat, Apr 26, 2008 at 7:39 PM, chromatic [EMAIL PROTECTED] wrote:
On Friday 25 April 2008 10:50:24 Will Coleda wrote:
Miscellaneous build warnings that need to be cleaned up.
src/key.c:306: warning: switch missing default case
Fixed in 27195.
compilers/imcc/imclexer.c:4288:
Good idea!
I'll add the file (if nobody beats me to it).
BTW, I think it'd be good to keep Squaak up to date, meaning that once
return statements are supported in PAST, that these are added as well.
This way it can be used as a complete showcase, demonstrating all of
PAST.
As soon as PAST is
On Tue, Apr 22, 2008 at 7:52 AM, Patrick R. Michaud [EMAIL PROTECTED] wrote:
Tonight I resolved RT#52838 and RT#52840, eliminating the saveall/restoreall
opcodes, the register stack, and fixing up tests and other items
to avoid save/restore/etc. opcodes.
I've also created a userstack
hi,
Currently, the pct tutorial language is out there, mostly on the
parrotblog entries, and I uploaded a .zip onto the wiki.
However, updating it is now a pain, because I have to recreate a .zip
and replace it on the wiki.
What do people think about adding it in the examples directory? At
first
On Mon, Apr 21, 2008 at 8:25 PM, Patrick R. Michaud [EMAIL PROTECTED] wrote:
On Mon, Apr 21, 2008 at 10:19:08AM -0700, chromatic wrote:
I'm still exploring the Rakudo build progress as a profiling target for
likely
optimizations. After this weekend's work, I have src/gen_actions.pir
On Mon, Apr 21, 2008 at 8:41 PM, Patrick R. Michaud [EMAIL PROTECTED] wrote:
On Mon, Apr 21, 2008 at 08:34:49PM +0100, Klaas-Jan Stol wrote:
hi,
Currently, the pct tutorial language is out there, mostly on the
parrotblog entries, and I uploaded a .zip onto the wiki.
However
On Fri, Apr 11, 2008 at 5:32 AM, Patrick R. Michaud [EMAIL PROTECTED] wrote:
With some recent PCT-related changes I think we may want to
update the tutorials a bit.
1. Remove the custom List class.
ResizablePMCArray now has built-in shift/unshift/push/pop
methods, so we can use it
On Mon, Apr 14, 2008 at 8:10 AM, Senaka Fernando [EMAIL PROTECTED] wrote:
On Mon, Apr 14, 2008 at 6:33 AM, chromatic [EMAIL PROTECTED] wrote:
On Sunday 13 April 2008 08:14:11 Senaka Fernando wrote:
The build of Parrot fails with g++, which is a possible indication that
it
fails
On Mon, Apr 14, 2008 at 12:26 AM, via RT Bob Rogers
[EMAIL PROTECTED] wrote:
# New Ticket Created by Bob Rogers
# Please include the string: [perl #52858]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=52858
IMCC's macro processor doesn't currently allow for uniquely generated
variable names. It's in the pdd (19), but not yet implemented.
You're right in that it only works for labels.
kjs
On Mon, Apr 14, 2008 at 1:32 PM, François Perrad
[EMAIL PROTECTED] wrote:
In Lua libraries, I wrote many
Hi,
these are good improvements! It will also improve performance a bit I think.
currently I don't really have much time to work on it, but I will in
maybe a week or so (or 2 weeks, possibly)
If people are looking for additional Exercises I suggest these are nice :-)
kjs
On Fri, Apr 11, 2008
Hi Geoffrey,
thanks for your reply and your thoughts. Please keep in mind it was
not a proposal to remove this long-invocation syntax, it just came to
mind when I realized that it's not used that much.
On Thu, Apr 3, 2008 at 5:17 PM, Geoffrey Broadwell [EMAIL PROTECTED] wrote:
On Wed,
hi,
i have some remarks/proposals on the current PDD 19 (PIR).
It already is full with proposals and issues that must be resolved
before it can be pushed out of draft status, but I figured now is the
time (as it will soon be worked on, I heard)
shall i provide this as a patch, or can i go ahead
I'm a bit confused on how lexicals are supposed to work. Below is a
simple example, which looks more or less on code generated by PCT for
a try/catch statement.
in the exception handler, a new Undef is created in $P0. When leaving
this line, this code won't work. When commenting out this line, it
On Tue, Apr 1, 2008 at 2:37 PM, Patrick R. Michaud [EMAIL PROTECTED] wrote:
On Tue, Apr 01, 2008 at 01:23:38PM +0200, Klaas-Jan Stol wrote:
in the exception handler, a new Undef is created in $P0. When leaving
this line, this code won't work. When commenting out this line, it
will print
Hi,
Although the patch is appreciated, I think it's better to keep it
empty; if you don't set a prompt, there shouldn't be one. I do not
know a language that has an empty prompt, but I'm sure there is.
Anyway, I think an empty prompt is a better default.
my 2c,
kjs
On Mon, Mar 31, 2008 at 12:09
On Fri, Mar 28, 2008 at 2:20 AM, Patrick R. Michaud [EMAIL PROTECTED] wrote:
On Thu, Mar 27, 2008 at 10:33:54PM +0100, Klaas-Jan Stol wrote:
On Wed, Mar 26, 2008 at 6:30 PM, Patrick R. Michaud [EMAIL PROTECTED]
wrote:
On Wed, Mar 26, 2008 at 02:25:06PM +0100, Klaas-Jan Stol wrote
On Fri, Mar 28, 2008 at 1:41 PM, Patrick R. Michaud [EMAIL PROTECTED] wrote:
On Fri, Mar 28, 2008 at 10:51:16AM +0100, Klaas-Jan Stol wrote:
Attached is a patch implementing:
* ++ and -- postfix operators, implemented as n_sub and n_add (taking
1 as the 3rd operand), this is because
thanks for the clarifications;
attached an updated patch including some tests.
I left out += and friends for now.
kjs
On Fri, Mar 28, 2008 at 4:18 PM, Patrick R. Michaud [EMAIL PROTECTED] wrote:
On Fri, Mar 28, 2008 at 02:41:28PM +0100, Klaas-Jan Stol wrote:
On Fri, Mar 28, 2008 at 1:41 PM
On Wed, Mar 26, 2008 at 6:30 PM, Patrick R. Michaud [EMAIL PROTECTED] wrote:
On Wed, Mar 26, 2008 at 02:25:06PM +0100, Klaas-Jan Stol wrote:
having used NQP a bit, I feel like I'm missing a few things. I'm not
entirely sure what the fate of NQP is; will it always be a bootstrap
stage
On Thu, Mar 27, 2008 at 6:48 PM, Ovid
[EMAIL PROTECTED] wrote:
Hi all,
Trying to work through the tutorial
(http://www.parrotblog.org/search/label/tutorial) and am trying to
finish Episode 4 with catch blocks. The grammar in Episode 3 has this:
try-statement ::= 'try' block 'catch'
hi,
having used NQP a bit, I feel like I'm missing a few things. I'm not
entirely sure what the fate of NQP is; will it always be a bootstrap
stage for Perl 6,or is it a tool for now and will it be discarded
later on.
Anyway, if NQP is to stay, the following features would come in handy,
IMHO. I
hi,
i've been working on an actions file for the NQP compiler, written in
NQP. It can be found in compilers/nqp/bootstrap
to build it, go to the compilers/nqp directory, and type make boot
It seems to work pretty nicely, except that there's some weirdness going on.
The problem seems to be that
after reading this tutorial you shouldn't have too much trouble
implementing SmallTalk (SmallSquawk?) :-)
the only issue is to find a proper grammar to stick with; effectively
all statements are PAST::Op( :pasttype('call') ) or
:pasttype('callmethod') (depending on your implementation, I think the
Hi,
Attached are the 4 most important files of my implementation of the
PCT tutorial language, Squaak.
Ideally, these files would be accessible online through the tutorial
(on parrotblog), but I don't know if that's possible.
kjs
grammar.pg
Description: Binary data
actions.pm
Description:
Hi François,
lua on parrot seems to have improved a lot, indeed.
It's looking really good.
Some remarks:
* is it possible to show the generated PIR? I can't get life.lua
(included with lua distr.), and I'd like to see what's going on under
the hood.
* running (n)make fails for me on windows,as I
On Tue, Mar 18, 2008 at 2:41 AM, James Keenan via RT
[EMAIL PROTECTED] wrote:
On Tue Feb 20 00:31:58 2007, kjs wrote:
Fortunately, in this case it looks to me as though t/pmc/sub.t
does have tests that check for proper execution of multiple
:load subs. So I think this ticket can be
On Tue, Mar 18, 2008 at 3:03 AM, James Keenan via RT
[EMAIL PROTECTED] wrote:
On Wed Jul 05 00:24:34 2006, [EMAIL PROTECTED] wrote:
Done, and I also added Vishal as a requestor on the relevant tickets.
The discussion appears to have been wrapped up, but the ticket was never
On Sun, Mar 16, 2008 at 11:04 PM, chromatic [EMAIL PROTECTED] wrote:
On Saturday 23 February 2008 14:23:19 Klaas-Jan Stol wrote:
On Sat, Feb 23, 2008 at 5:00 PM, Ron Blaschke [EMAIL PROTECTED] wrote:
The issue seems to be caused by languages/c99/src/preamble, where:
.local
On Wed, Mar 12, 2008 at 9:28 PM, via RT Bernhard Schmalhofer
[EMAIL PROTECTED] wrote:
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #51662]
# in the subject line of all future correspondence about this issue.
# URL:
On Mon, Mar 10, 2008 at 12:11 PM, James E Keenan [EMAIL PROTECTED] wrote:
A developer who recently attended Perl Seminar NY asked me this
question, to which I didn't have the answer.
Hi James,
Is Parrot embeddable into C programs, like Perl is ?
Can anyone advise? Thanks.
1 - 100 of 366 matches
Mail list logo
