Gregor N. Purdy <[EMAIL PROTECTED]> wrote:
> All --
> I just did a CVS update, and I had to make the following changes
> to get it to compile
Why did it not compile? What error message?
> ... (I also had to delete and update
> languages/imcc/parser.[hc], which I think was expected).
Not expecte
Ask Bjoern Hansen <[EMAIL PROTECTED]> wrote:
> Hi,
> We setup a development list for ponie.
May I ask: What is ponie?
> - ask
leo
Michal Wallace <[EMAIL PROTECTED]> wrote:
> But is there a better solution for first time
> users?
I have checked in a "final" solution for this never ending story.
It replaces the bison/lex build line with:
echo ... or REM ...
by default.
I have added a Configure option C<--maintainer> to
Tupshin Harper wrote:
I'm not a "GCC person", but I do have an interest in this working. I did
some exploratory work (mostly getting familiar with the GCC backend
mechanism and with PASM), and quickly ran into what appeared to be
fundamental roadblocks regarding gcc's predilection for generatin
Hi,
We setup a development list for ponie.
email
[EMAIL PROTECTED]
to subscribe.
- ask
--
http://www.askbjoernhansen.com/ - http://develooper.com/
All --
I noticed that there are many files with copyrights of
"when this is determined...", while some files have a
copyright of Yet Another Society. Seems like they should
all be Yet Another, or none should be...
Regards,
-- Gregor
--
Gregor Purdy[EMAIL PROTECTED]
All --
I just did a CVS update, and I had to make the following changes
to get it to compile (I also had to delete and update
languages/imcc/parser.[hc], which I think was expected).
I didn't check it in because I'm not sure if the stuff I commented
out is really supposed to go (although recent p
Leopold Toetsch wrote:
Why the smilies ;-) Parrot is a fine processor well suited for an
optimizing compiler and with a reasonable architecture. Its not the
first time that I'm thinking of such a hack.
... though it would need some extensions at both sides.
Are some gcc people listening?
leo
I
Luke Palmer <[EMAIL PROTECTED]> wrote:
>> PS are there & | ^ Perl6 operators too, that do either int or stringwise
>> operations depending on the left operand?
> No, those are the junction operators (see Quantum::Superpositions),
> which are going to be fun to write...
A yes, thanks.
Forgot about
> Comments welcome,
> leo
>
> PS are there & | ^ Perl6 operators too, that do either int or stringwise
> operations depending on the left operand?
No, those are the junction operators (see Quantum::Superpositions),
which are going to be fun to write...
Luke
Michal Wallace wrote:
Hey all,
Basically, IMCC fails to build on a fresh CVS
checkout because of the dates on the imcparser.c
and imcparser.h files.
[ snip ]
http://nntp.x.perl.org/group/perl.perl6.internals/16419
I've changed my checkin scripts again, so that now the generated files
get tou
--- David Storrs <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 08, 2003 at 05:52:04PM -0700, Austin Hastings wrote:
> >
> > --- Jonadab the Unsightly One <[EMAIL PROTECTED]> wrote:
> > > Am I now thinking clearly?
> > >
> > I don't think so.
> >
> > If you've created two separate arrays that happen
We have a rather inconsistent usage of $subject.
I think simplest would be to have no explicit newline in the text and
let the exception handler print one.
leo
Hey all,
I've been following parrot for a while and finally
decided to try it out. Anyway, I ran into a snag.
Hopefully this is the right place to report this.
Basically, IMCC fails to build on a fresh CVS
checkout because of the dates on the imcparser.c
and imcparser.h files.
Looks like this
On Tue, Jul 08, 2003 at 05:52:04PM -0700, Austin Hastings wrote:
>
> --- Jonadab the Unsightly One <[EMAIL PROTECTED]> wrote:
> > Am I now thinking clearly?
> >
> I don't think so.
>
> If you've created two separate arrays that happen to start with related
> values, then the changes to the first
After removing a bunch of methods, I'd like to add some;-)
The Perl6 operators +& +| +^ and ~& ~| ~^ need support. While we have
the former, we are lacking the stringwise operations.
Now: Proposed: New:
bitwise_or_int(P,P,I)bitwise_or_int_i bitwise_or_str_s(P,P,
Kevin Harris (via RT) wrote:
Hello,
On a single-processor Slackware 9 system, I experience (consistantly)
the following error when running "make test":
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/pmc/i
- the {g,s}et__keyed_int vtables take a plain INTVAL now, no more
a pointer to one
- the src_key argument of pmc_keyed functions is gone
- all arithmetic, logical and boolean multi keyed vtables are gone
- as well as set P[k], P[k]
All these were unused. Tests still pass.
This did reduce the size
Leo --
No problem. I saw the smiley, but SCNR was new to me.
"we cool"
:)
Regards,
-- Gregor
On Wed, 2003-07-09 at 02:08, Leopold Toetsch wrote:
> Gregor N. Purdy wrote:
>
> > IIRC, that has been the policy during previous freezes.
> >
> > However, I can stop tinkering if its getting in an
During moving and looking at the IO tests, I was a little confused about
hacks_3 (now io_9) which wrote to stdout (now to the file).
Anyway I have added a check in io.c, if a file is opened for writing. Is
that ok, or should the lower layers just do the Rigth Thing?.
leo
# New Ticket Created by Kevin Harris
# Please include the string: [perl #22902]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=22902 >
Hello,
On a single-processor Slackware 9 system, I experience (consistantly)
the follow
Steve Fink <[EMAIL PROTECTED]> wrote:
> I would remove the rxstack, but I didn't want to break the closest
> thing we have to a regex engine until I or someone else managed to
> release a different working implementation. The particular technique
> of using a single stack tied directly the interpr
Gregor N. Purdy wrote:
IIRC, that has been the policy during previous freezes.
However, I can stop tinkering if its getting in anyone's
way or on anyone's nerves...
Some smilies and a "SCNR" must have been lost. The change was small,
doesn't break anything and wouldn't be of any harm, *if* we ha
23 matches
Mail list logo
