Dan Sugalski wrote:
Okay, I've finally stopped waffling. The current PMC structure is now
officially frozen, modulo the odd twiddling to it.
Doese odd twiddling include the Buffer/PMC unification?
... As such, I've added a
pmc.ops file and I'm starting to add in ops to read and write bits o
I agree that it seems wrong to change the name of an already established
language. However, I also don't like the fact that something with the name
"Brainfuck" comes with the core of parrot. What if we moved its
distribution out of CVS and just put it on the webpage, or something of that
nature?
Gopal V wrote:
If memory serves me right, Leopold Toetsch wrote:
Is there any other way to feed imcc code other than via writing to a
file and running it ?...
Not currently.
Dan was saying something like a C interface to IMCC which bypasses the
parser and lexer phases was possible ?
Yes
Steve Fink (via RT) wrote:
- The .local directive requires a type. I fixed the documentation.
- The lexer allows an optional dot in front of a parrot op or
identifier, but then seems to assume that the dot is not there. So I
took it off.
- A few trivial things: parenthesized a macro arg for s
On 12/03/2002 2:27 PM, Michael Lazzaro wrote:
I think we've been gravitating to a "language reference", geared
primarily towards intermediate/advanced users. Something much more
rigorous than beginners would be comfortable with (since it defines
things in much greater detail than beginners wou
> Date: Tue, 03 Dec 2002 18:39:27 -0500
> From: James Mastros <[EMAIL PROTECTED]>
>
> Huh? In that case, somebody should tell Angel Faus; "Numeric literals,
> take 3" says 0c777, and nobody disented. IIRC, in fact, nobody's
> descented to 0c777 since it was first suggested.
Well, except Larry.
On Tue, 3 Dec 2002, Brent Dax wrote:
> Andy Dougherty:
> # Well, I'll speak up. I find the name needlessly crude and
> # offensive. I see no reason to use such a name and would
> # strongly prefer that Parrot didn't. Parrot is a collective
> # project representing a community of developers,
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #18862]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18862 >
Without the following patch, Sun's cc compiler complained:
"jit.c", line 504: non-con
There are some files in parrot that have names common in the first 8
characters. This will cause problems if someone tries to compile Parrot on
DOS. Is DOS an intended target, or should we not worry about this?
/core_ops*.c
/docs/packfile*.pod
/examples/assembly/benchmarks/gc*.pasm
/icu/source/dat
Mr. Nobody wrote:
> There are some files in parrot that have names common in the first 8
> characters. This will cause problems if someone tries to compile Parrot on
> DOS. Is DOS an intended target, or should we not worry about this?
my vote is NO. let us bury 8.3 very, very deep in the ground.
All --
I thought that something like what follows:
goto _foo
end
_foo:
print "Howdy!\n"
end
would be legal imcc input, but I get:
last token = [(null)]
(error) line 1: parse error
Didn't create output asm.
instead of happiness. I'm trying to learn enough IMCC th
--- [EMAIL PROTECTED] wrote:
> I thought that something like what follows:
>
> goto _foo
> end
> _foo:
> print "Howdy!\n"
> end
>
> would be legal imcc input
IMCC requires you to put everything in .subs. So it should be something like
..sub main
goto _foo
end
_foo:
print "H
--- "Mr. Nobody" <[EMAIL PROTECTED]> wrote:
> ..sub main
> ..end
Except without those extra dots. Stupid mailer.
__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
At 10:26 PM -0800 12/3/02, Brent Dax wrote:
Andy Dougherty:
# On Thu, 21 Nov 2002, Leon Brocard wrote:
#
# > ps You might be concerned about the name. Well, CPAN has a module
# >which matches /fuck/ too. However, if everyone really thinks
# >it is a problem, I don't see a problem with s/fu
At 9:35 AM +0100 12/4/02, Leopold Toetsch wrote:
Dan Sugalski wrote:
Okay, I've finally stopped waffling. The current PMC structure is
now officially frozen, modulo the odd twiddling to it.
Doese odd twiddling include the Buffer/PMC unification?
Yup. This'd be a good time to do that.
...
At 6:58 AM -0800 12/4/02, Mr. Nobody wrote:
There are some files in parrot that have names common in the first 8
characters. This will cause problems if someone tries to compile Parrot on
DOS. Is DOS an intended target, or should we not worry about this?
DOS isn't an intended compilation target,
[EMAIL PROTECTED] wrote:
All --
I thought that something like what follows:
goto _foo
end
_foo:
print "Howdy!\n"
end
Works fine *if* you insert your example into ".sub" ... ".end":
..sub _test
goto _foo
end
_foo:
print "ok 1\n"
end
..end
Regards,
-- Gregor
leo
Thanks for the tip.
I think I can use that to work around the limitation. It makes it
unnatural to
have a script with the pattern:
some code
some subroutine definitions
some more code, calling the subroutines.
Which Jako permits.
It looks like I can wrap all the bits of miscella
Dan Sugalski wrote:
At 9:35 AM +0100 12/4/02, Leopold Toetsch wrote:
Doese odd twiddling include the Buffer/PMC unification?
Yup. This'd be a good time to do that.
So the question is, how should the final "Parrot Object" look like. I
did send a test program on Oct. 25th which got warnoc
Andy Dougherty (via RT) wrote:
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #18862]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18862 >
The original style was clearer but this at least comp
All --
Before I go changing the Jako compiler, I'd like some feedback. There are
three files
below. First is fact.jako, the factorial algorithm expressed as a Jako
subroutine with
some mainline code that calls it. Then comes fact.imc, which I produced by
hand-
editing the fact.pasm file that ja
It's o, not c.
Larry
[EMAIL PROTECTED] wrote:
And just ignore the spurrious 'ret' instructions imcc generates to
"properly"
terminate each of the "subroutines" (
These "ret" ins are remnants from the ret => .end change - they will go
away.
leo
If memory serves me right, Leopold Toetsch wrote:
> Yes, but I think, that incompatible changes shouldn't be necessary any
> more - sorry for breaking things.
No problemo ... I just hate working on the same things again ...
> SymReg *r = mk_ident(char *name, char type)
> iANY("add", R3(r0,r
On Wed, 4 Dec 2002, Dan Sugalski wrote:
> It's not our language to rename, though, so either the creator OKs it
> or it goes. If there's an acceptable alternative spelling, we can use
> that too.
The web site in the README in the parrot sources uses 'bf', as does at
least one of the sites refer
At 11:41 AM -0500 12/4/02, Andy Dougherty wrote:
On Wed, 4 Dec 2002, Dan Sugalski wrote:
It's not our language to rename, though, so either the creator OKs it
or it goes. If there's an acceptable alternative spelling, we can use
that too.
The web site in the README in the parrot sources use
On Mardi 3 Décembre 2002 23:24, Nicholas Clark wrote:
> The perl foundation was able to provide some grants towards work on
> this project and perl6. However, fund raising wasn't sufficient to
> keep grants going full time.
About two months ago, I asked the perl foundation about the grants, and
K
[EMAIL PROTECTED] wrote:
All --
Before I go changing the Jako compiler, I'd like some feedback.
.sub dummy
goto main
_fact:
...
ret
main:
..
call _fact
...
.end
"goto"s to other subs are not subject of address fixup (though this
could be changed).
leo
On Wed, Dec 04, 2002 at 10:32:41AM -0500, Dan Sugalski wrote:
> At 6:58 AM -0800 12/4/02, Mr. Nobody wrote:
> >There are some files in parrot that have names common in the first 8
> >characters. This will cause problems if someone tries to compile Parrot on
> >DOS. Is DOS an intended target, or sho
At 10:01 AM -0800 12/4/02, Michael G Schwern wrote:
On Wed, Dec 04, 2002 at 10:32:41AM -0500, Dan Sugalski wrote:
At 6:58 AM -0800 12/4/02, Mr. Nobody wrote:
>There are some files in parrot that have names common in the first 8
>characters. This will cause problems if someone tries to compile
On Wed, Dec 04, 2002 at 02:03:06PM -0500, Dan Sugalski wrote:
> >> DOS isn't an intended compilation target, no.
> >
> >Not even djgpp?
>
> Hadn't planned on it. What advantage does it give over windows?
It'll compile C programs on a 386/SX, 20M of disk, 4megs of RAM and some
form of DOS.
Dunno
On 12/4/02 2:16 PM, Michael G Schwern wrote:
> On Wed, Dec 04, 2002 at 02:03:06PM -0500, Dan Sugalski wrote:
DOS isn't an intended compilation target, no.
>>> Not even djgpp?
>>
>> Hadn't planned on it. What advantage does it give over windows?
>
> It'll compile C programs on a 386/SX, 20M o
At 11:16 AM -0800 12/4/02, Michael G Schwern wrote:
On Wed, Dec 04, 2002 at 02:03:06PM -0500, Dan Sugalski wrote:
>> DOS isn't an intended compilation target, no.
>
>Not even djgpp?
Hadn't planned on it. What advantage does it give over windows?
It'll compile C programs on a 386/SX, 20M of
We still need to verify whether we can have, in qq strings:
\033 - octal (p5; deprecated but allowed in p6?)
\o33 - octal (p5)
\x1b - hex (p5)
\d123 - decimal (?)
\b1001- binary (?)
and if so, if these are allowed too:
\o{777}
"Michael Lazzaro" <[EMAIL PROTECTED]> wrote
> Note that \b conflicts with backspace. I'd rather keep backspace than
> binary, personally; I have yet to feel the need to call out a char in
> binary. :-) Or we can make it dependent on the trailing digits, or
> require the brackets, or require back
On Wed, Dec 04, 2002 at 11:38:35AM -0800, Michael Lazzaro wrote:
: We still need to verify whether we can have, in qq strings:
:
:\033 - octal (p5; deprecated but allowed in p6?)
I think it's disallowed.
:\o33 - octal (p5)
:\x1b - hex (p5)
:\d12
Larry wrote:
: But I think we'd definitely like to introduce \d.
Can't, unless we change \d to in regexen.
Which we ought to be very wary of, given how very frequently it's
used in regexes.
Damian
On Wednesday, December 4, 2002, at 12:21 PM, Larry Wall wrote:
I think the general form is:
\0o33 - octal
\0x1b - hex
\0d123 - decimal
\0b1001- binary
\x and \o are then just shortcuts.
The general form could be
\0o[33] - octal
\0x[1b] - hex
> I think that solves all the problems we're having. We change \c to
> have more flexible meanings, with \0o, \0x, \0d, \0b, \o, \x as
> shortcuts. Boom, we're done. Thanks!
How far can we go with this \c thing? How about:
print "\c[72, 101, 108, 108, 111]";
will that print "Hello"?
On Mon, Dec 02, 2002 at 04:42:52PM -0500, Joseph F. Ryan wrote:
: >Has this been vetted? $(...)/etc seem to cover this case, and & being
: >a qq() metachar makes using qq() strings to print HTML/XML difficult.
:
:
: Well, it was in Apoc 2:
: http://www.perl.com/pub/a/2001/05/03/wall.html#rfc 2
On Wednesday, December 4, 2002, at 11:47 AM, Larry Wall wrote:
This is great stuff, and I think it solves everything we were talking
about. Joseph, can you edit your doc to match all this? (If not, just
lemme know and I can help.)
If anyone can think of any more issues w/ strings and hered
On Wednesday, December 4, 2002, at 11:50 AM, Dave Whipp wrote:
ps. how did this thread migrate from p6d to p6l?
By popular request. If we have something we think will be even
remotely controversial, we'll move it to p6l for debate, then use p6d
to summarize the outcome. That will concentra
SUMMARY
Proposal for the "purge" command as the opposite of "grep" in the same way
that "unless" is the opposite of "if".
DETAILS
I've lately been going a lot of greps in which I want to keep all the
elements in an array that do *not* match some rule. For example, suppose
I have a list of membe
(The post about 'purge' just made me remember this idea)
Lets say you have a list of program arguments.
@ARGV = ('foo', '--bar=baz', 'yar');
and you want to seperate that into two lists. One of switches and one of
normal args. You can't just use a grep, you'd have to do this:
my @swit
Miko O'Sullivan [mailto:[EMAIL PROTECTED]] wrote:
> SUMMARY
>
> Proposal for the "purge" command as the opposite of "grep" in
> the same way that "unless" is the opposite of "if".
I like it.
But reading it reminded me of another common thing I do
with grep: partitioning a list into equivalence
> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> Date: Wed, 4 Dec 2002 18:26:17 -0800
> From: Michael G Schwern <[EMAIL PROTECTED]>
> Content-Disposition: inline
> Sender: Michael G Schwern <[EMAIL PROTECTED]>
> X-SMTPD: qpsmtpd/0.12, http://develooper.com/code/qpsmtpd/
>
> (The post abou
On Wed, Dec 04, 2002 at 08:08:48PM -0700, Luke Palmer wrote:
> About your idea, though, I'm rather indifferent. However, a friend of
> mine once asked me if Perl had "search" or "find" operation, returning
> the I of matching elements. Now am I just being braindead, or
> is Perl actually missing
> Date: Wed, 4 Dec 2002 19:21:27 -0800
> From: Michael G Schwern <[EMAIL PROTECTED]>
>
> On Wed, Dec 04, 2002 at 08:08:48PM -0700, Luke Palmer wrote:
> > About your idea, though, I'm rather indifferent. However, a friend of
> > mine once asked me if Perl had "search" or "find" operation, returning
# New Ticket Created by mrnobo1024
# Please include the string: [perl #18876]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18876 >
Currently imcc.y has a label called "OUT" in the command-line argument
parsing code. This
I've renamed the brainfuck directory to bf, per Dan's request.
I _did not_ do the usual magic I do to keep both the old and new names
valid.
Thus - according to CVS, the brainfuck directory never existed, only
one called bf.
I updated the MANIFEST, but did not update anything else.
-R
--
On Wed, 4 Dec 2002, Miko O'Sullivan wrote:
>
> FWIW, I came up with "purge" because my first inclination was to spell
> "grep" backwards: "perg". :-)
While "purge" is cute, it certainly is not obvious what it does. Of
course neither is "grep" unless you are an aging unix guru...
How about somet
mrnobo1024 (via RT) wrote:
# New Ticket Created by mrnobo1024
# Please include the string: [perl #18876]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18876 >
Currently imcc.y has a label called "OUT"
Thank you,
appli
52 matches
Mail list logo
