In the interests of brevity, I cut huge tracts of quoted text.
On Mon, 6 May 2002, Brent Dax wrote:
> (FYI, I'm the main author of Parrot's rx package.)
>
I'm pleased to meet you.
> Mark Kvale:
> # Warning: this is a long message, a small paper really. The
> # So creating (A) or (B) wil
--
On Mon, 6 May 2002 16:26:16
Dan Sugalski wrote:
>*Alot of good answers to questions*
Appreciate the descent from the mountain to help clear things up down here.
-Erik
Is your boss reading your email? Probably
Keep your messages private by using Lycos Mail.
Sign up today at http
(FYI, I'm the main author of Parrot's rx package.)
Mark Kvale:
# Warning: this is a long message, a small paper really. The
# synopsis is that I have created a simple regex compiler with
# multiple backends to test proposed regex coding schemes.
# Details and test results are below.
#
# Hi al
Warning: this is a long message, a small paper really. The synopsis is
that I have created a simple regex compiler with multiple backends to
test proposed regex coding schemes. Details and test results are
below.
Hi all,
One of the upcoming decisions that needs to be made is on the design
of th
The broken 64bit systems seem to be related to compiling
Parrot with a different wordsize than Perl5, since I'm currently
getting byteorder from Perl5 Config.pm.
I guess we will have to compute it ourselves after Parrot
has picked what type to use for INTVAL/opcode_t
-Melvin
I forgot to announce the call for questions here (sorry), but the
answers 9and the questions) to the first round of Ask The Parrot have
been posted over on use.perl.
http://use.perl.org/article.pl?sid=02/05/06/179233 for the interested.
--
Dan
On Mon, 6 May 2002, Melvin Smith wrote:
> At 01:44 PM 5/6/2002 -0400, you wrote:
> >When I try to build parrot with gcc, I get 754 warnings. Obviously I
> >won't post them all here, but some typical ones are:
>
> I'm working on some of them. I saw quite a few issues while
> reworking the byte
On Mon, May 06, 2002 at 10:53:11AM +1000, Damian Conway wrote:
> Allison asked:
>
> > Hmmm... would C not have the same problem as C? It also
> > "can't decide whether to execute until it knows whether the loop is
> > going to iterate again".
>
> Yes, it does.
Then I agree with Miko, it's not
- Original Message -
From: "David Whipp" <[EMAIL PROTECTED]>
> Is this the same as saying that C can be followed by
> *any* statement? If not, then we would need user-defined
> control statements (a property on a sub?) that can be used
> in the "else" context.
Perhaps C is a binary operat
At 01:44 PM 5/6/2002 -0400, you wrote:
>When I try to build parrot with gcc, I get 754 warnings. Obviously I
>won't post them all here, but some typical ones are:
Firstly I just did a big patch to make the bytecode portable, so thats
the reason you are seeing packfile issues, however they aren't
Oh. Sorry. I suppose there was no discussion because there were no
objections. I support it strongly. But everyone's already heard my
opinion, and my opinion, and my opinion about it, so I'll be quiet now.
Luke
On 6 May 2002, Aaron Sherman wrote:
> It's odd, folks are still talking about the
Miko O'Sullivan [mailto:[EMAIL PROTECTED]] wrote:
> Sorry, I thought I'd expressed agreement at some point. I like the
> "else\s+(if|while|for|loop)" construct very much, and I think the
> programmers of the world would like it too. I know a some people have
> issues with "where's the if" but it
> It's odd, folks are still talking about the icky elsstuff, but I never
> saw any discussion of my BNF proposal. Was it that no one saw it, that
> my BNF was too rusty, or the idea of abandoning elsif for (in
> pseudo-ebnf)
Sorry, I thought I'd expressed agreement at some point. I like the
"els
On Mon, 2002-05-06 at 12:22, [EMAIL PROTECTED] wrote:
> |Oh! I have an idea! Why don't we make the lexer just realize a prefix
> |"els" on any operator. Then you could do C. :P
> |
> |My point is that, IMO, this whole "els" thing is completely preposterous.
> |I'm the kind of person that likes t
I haven't been following Parrot lately, but I just checked out the current
version to see how well it gets along with my current perl-5.7.3. My
perl is compiled with IV='long long', which means Parrot will default
to using 'long long' as INTVAL. (I suspect this is likely to be a
reasonably commo
On Mon, 6 May 2002 [EMAIL PROTECTED] wrote:
> |> Damian, now having terrible visions of someone suggesting C ;-)
> |
> |Then may I also give you nightmares on: elsdo, elsdont, elsgrep, elstry ...
>
> ]- unlessdo, unlesdont, unlessgrep, unlesstry
What's with this? unless doesn't do that,
perfect... in fact during the middle of the read someting similar come to my mind..
i.e the best way should be to have several in-loop-proprietes that we can test and
decide what to do ...
There have to be CAPITALISED words only for the block stuff ...
raptor
|> Damian, now having terrible visions of someone suggesting C ;-)
|
|Then may I also give you nightmares on: elsdo, elsdont, elsgrep, elstry ...
]- unlessdo, unlesdont, unlessgrep, unlesstry
what about "elsunless/unlesselse" then :")
|On Mon, Apr 29, 2002 at 02:55:09PM -0500, Allison Randal wrote:
|> I still don't like the idea of Cs on loops. I already do an
|> instant double take with C of "Where's the if?" (with visions of
|> old Wendy's commercials dancing in my head).
|
|Me too. That's why the looping "else" should be s
|Oh! I have an idea! Why don't we make the lexer just realize a prefix
|"els" on any operator. Then you could do C. :P
|
|My point is that, IMO, this whole "els" thing is completely preposterous.
|I'm the kind of person that likes to keep down on keywords. And I never
|liked Perl5's C anyway; I
On Sat, 4 May 2002, Brent Dax wrote:
> Melvin Smith:
> # I have a patch almost complete that makes Parrot handle
> # bytecode files across platforms (does endian and wordsize
> # transform), but there is one glaring non-portability, and
> # that is that we are storing floating point constants
Although the tidying up of resources.c is not complete yet, I decided to
implement COW strings anyway.
This implementation handles the following:
Copied strings and substrings are COWed instead of copied (i.e. new string
header only); this applies to normal and constant strings.
Functions that al
22 matches
Mail list logo
