o
builtins. Personally I'd have it be 'use perl5' (it's the difference
between making a new pragma and defining a third meaning for require [or
redefining its current meaning]) but that's a minor detail. Unfortunately,
it may be too late. Oh well...
--Brent Dax
Excuse typos, it's hahd to write on a Palm...
first {...}
sort {...}
last {...}
} @ary;
--Brent Dax
Excuse typos, it's hahd to write on a Palm...
"Brent" == Brent Dax [EMAIL PROTECTED] writes:
Brent @s = schwartzian(
Please, if we're going to add an operator, let's not call it schwartzian!
I have enough trouble already telling people how to spell my name. :)
Which is why my real suggestion was a 'tsort' ('tsort' eq
dd
New Magic to Perl.
- Keep your eyes on
modularity. Modularity is by
far the best concept where
complexity could be hidden.
- Don't forget usability. This
is after all the point why
people use Perl in the first
place.
Never.
So the basic question is, readability or usability? I say usability.
--Br
-Original Message-
From: Jarkko Hietaniemi [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 26, 2001 15.43
To: Brent Dax
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Perl culture, perl readabillity
The reward? English-speaking children learn what is arguably the most
flexible
I think we were all just stunned by the sheer brilliance. :^) That package
thing is pretty damn clever...
--Brent Dax
[EMAIL PROTECTED]
This e-mail is a circumvention device as defined by the Digital Millennium
Copyright Act.
#qrpff
s''$/=\2048;while(){G=29;R=142;if((@a=unqT="C*",_
[EMAIL PROTECTED] wrote on 4/5/01 12.15:
2. package vs. module/class
Whoa. This is so simple yet so sublime. It solves so many issues in one
swoop. Cool.
Assuming Perl6 will be parsing Perl5 code? Hmmm. That's interesting. Forget
p52p6 and the whole 80/20 thing, we could potentially hit the
name"? Having Perl_foo and PL_foo is a bit confusing anyway. I
like Perl_foo and PERL_foo--it makes it very clear what things are while
making sure we keep our own little 'namespace'.
--Brent Dax
Excuse typos, it's hahd to write on a Palm...
about $a cat $b? That keeps the theme of strings using words and
numbers using symbols--like eq vs. ==.
--Brent Dax
theme)
So, what else would we do with our new inline #! notation? Hmm...
$foo=$bar;
#!comment
yadda yadda yadda
blah blah blah
foo bar baz
#!endcomment
$bar.=$baz;
Maybe? Possibly? No? Darn...
--Brent Dax
[EMAIL PROTECTED]
sense? Or should I be returned to my straightjacket?
:^)
--Brent Dax
[EMAIL PROTECTED]
(or maybe it is?)
#i could have used has/have instead, but is/are makes more sense here
--Brent Dax
[EMAIL PROTECTED]
...
}
Even if it was actually implemented some other way, all we'd need to do is
make sure that we can attach properties to it somehow. (The Cproperty
property would itself attach to a variable, not a value.)
--Brent Dax
[EMAIL PROTECTED]
Simon Cozens:
On Sun, May 20, 2001 at 01:09:28AM -0700, Brent Dax wrote:
This also reads like English:
Is foo constant?
Until you realise that in order to actually use it sensibly, you'll
have to say something like
if (is $foo constant)
instead of (as I would prefer)
if ($foo
. (In general, I think that syntactic
operators like parenthesis and comma should behave the same regardless of
scalar/list context, while functions should behave differently. That's just
my bias, though. Feel free to laugh at me if I'm wrong here.)
--Brent Dax
[EMAIL PROTECTED]
I'd think that @ISA would be copied to .ISA on object instantiation, and
after that the two wouldn't have anything to do with each other. We could
set up one of those cool copy-on-write locks everyone's been talking about
to save memory too.
Or we could have it default to @ISA if .ISA doesn't
print Baz: @(Baz('a', 'b')); #prints Baz: a b
print $(Context); #prints scalar
print @(Context); #prints list
Does that check out right?
Thanks,
--Brent Dax
[EMAIL PROTECTED]
with while I was writing this: Could
inheritance be a
property?
class My::Class is a('Other::Class'); #My::Class::ISA=('Other::Class')
--Brent Dax
[EMAIL PROTECTED]
an idea,
# but you are saying it wrong if you do.
There are plenty of things that have no counterpart in boolean logic. Where are loops
defined in
Boolean logic?
--Brent Dax
[EMAIL PROTECTED]
.)
Thanks,
--Brent Dax
[EMAIL PROTECTED]
# -Original Message-
# From: Uri Guttman [mailto:[EMAIL PROTECTED]]
# Sent: Friday, August 24, 2001 8:56 PM
# To: [EMAIL PROTECTED]
# Cc: [EMAIL PROTECTED]
# Subject: Re: Will subroutine signatures apply to methods in Perl6
#
#
# BD == Brent Dax [EMAIL PROTECTED] writes:
...
# BD Two
I was thinking about Perl 6 today, and thought of something: if the
sigil is now part of a variable's name, does that mean that $Foo::bar
should actually be Foo::$bar in Perl 6?
--Brent Dax
[EMAIL PROTECTED]
level of indirection) while leveraging the gain
# from a split-level
# op despatch loop.
Not a bad idea. Allowing for optimizations later so they aren't
premature is usually a good idea. :^)
--Brent Dax
[EMAIL PROTECTED]
impossible to modify for different storage--it was far easier
to just write a new class with the same interface. Stupid, stupid,
stupid.
--Brent Dax
[EMAIL PROTECTED]
.
--Brent Dax
[EMAIL PROTECTED]
...and if the answers are inadequate, the pumpqueen will be overthrown
in a bloody coup by programmers flinging dead Java programs over the
walls with a trebuchet.
endian-ness and for reading precompiled
bytecode anyway, we might as well make it convenient...
--Brent Dax
[EMAIL PROTECTED]
...and if the answers are inadequate, the pumpqueen will be overthrown
in a bloody coup by programmers flinging dead Java programs over the
walls with a trebuchet.
) of the prototypes available for the
method is appropriate for those parameters. Its implementation is left
as an exercise to the reader. :^)
--Brent Dax (who finds it very amusing that the spell checker tried to
change Sugalski to Sealskin)
[EMAIL PROTECTED]
...and if the answers are inadequate
--Brent Dax
[EMAIL PROTECTED]
...and if the answers are inadequate, the pumpqueen will be overthrown
in a bloody coup by programmers flinging dead Java programs over the
walls with a trebuchet.
\-yes-call FOO--/
there could also be some more complicated situations, in which the
situations where the optimizations are invalid are harder to define.
I'd also suggest a different pragma:
use less 'optimization';
--Brent Dax
[EMAIL PROTECTED]
...and if the answers are inadequate
# -Original Message-
# From: Bryan C. Warnock [mailto:[EMAIL PROTECTED]]
# Sent: Saturday, September 01, 2001 3:01 PM
# To: Brent Dax; [EMAIL PROTECTED]
# Subject: Re: Deoptimizations
#
#
# On Saturday 01 September 2001 05:07 pm, Brent Dax wrote:
# Of course, the hard part is detecting
# -Original Message-
# From: Simon Cozens [mailto:[EMAIL PROTECTED]]
# Sent: Sunday, September 02, 2001 4:34 AM
# To: Brent Dax
# Cc: [EMAIL PROTECTED]
# Subject: Re: Should MY:: be a real symbol table?
#
#
# On Sun, Sep 02, 2001 at 03:13:09AM -0700, Brent Dax wrote:
# Is there any real
# -Original Message-
# From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
# Of Ken Fox
# Sent: Sunday, September 02, 2001 8:49 AM
# To: Brent Dax
# Cc: [EMAIL PROTECTED]
# Subject: Re: Should MY:: be a real symbol table?
#
# Brent Dax wrote:
# Is there any real reason my
# -Original Message-
# From: Sam Tregar [mailto:[EMAIL PROTECTED]]
# Sent: Sunday, September 02, 2001 1:23 PM
# To: Brent Dax
# Cc: [EMAIL PROTECTED]
# Subject: RE: Should MY:: be a real symbol table?
#
# On Sun, 2 Sep 2001, Brent Dax wrote:
#
# but in that case the inner my($x) could
# -Original Message-
# From: Dan Sugalski [mailto:[EMAIL PROTECTED]]
# Sent: Sunday, September 02, 2001 1:37 PM
# To: Brent Dax
# Cc: Simon Cozens; [EMAIL PROTECTED]
# Subject: RE: Should MY:: be a real symbol table?
#
#
# On Sun, 2 Sep 2001, Brent Dax wrote:
#
# Perhaps I wasn't
, string manipulation is done in special string registers, which
are *not* PMCs.
--Brent Dax
[EMAIL PROTECTED]
...and if the answers are inadequate, the pumpqueen will be overthrown
in a bloody coup by programmers flinging dead Java programs over the
walls with a trebuchet.
Note: some parts of this may seem a bit like a flame. This is
unintentional.
Ken Fox:
# Brent Dax wrote:
# What I'm suggesting is that, instead of the padlist's AV containing
# arrays, it should contain stashes, otherwise indistinguishable from
# the ones used for global variables
# -Original Message-
# From: Dan Sugalski [mailto:[EMAIL PROTECTED]]
# Sent: Monday, September 03, 2001 5:50 PM
# To: Brent Dax; Ken Fox
# Cc: Simon Cozens; [EMAIL PROTECTED]
# Subject: RE: Should MY:: be a real symbol table?
#
#
# At 05:30 PM 9/3/2001 -0700, Brent Dax wrote:
# As far
--Brent Dax
[EMAIL PROTECTED]
...and if the answers are inadequate, the pumpqueen will be overthrown
in a bloody coup by programmers flinging dead Java programs over the
walls with a trebuchet.
# -Original Message-
# From: Dan Sugalski [mailto:[EMAIL PROTECTED]]
# Sent: Monday
Simon Cozens:
# On Mon, Sep 03, 2001 at 04:05:26PM -0700, Brent Dax wrote:
# In other words, when you have sub foo {} in your code, it will be
# assigned an opcode number in the 'private' section. The
# global section
# is for things that are built-in to Parrot, while the
# private section
push P0, I3
load 2, I2
add I1, I2, I3
push P0, I3
(lather, rinse, repeat)
In the more general case, however (say, $x*1+$x*2+...$x*65) that's an
interesting question. Could we just do some fun stuff with lists? What
do real CPUs do?
--Brent Dax
[EMAIL PROTECTED
to be *that* powerful? If so, I think
I'll stay with the execution engine... :^)
--Brent Dax
[EMAIL PROTECTED]
...and if the answers are inadequate, the pumpqueen will be overthrown
in a bloody coup by programmers flinging dead Java programs over the
walls with a trebuchet.
Dan Sugalski:
# At 12:04 PM 9/6/2001 -0700, Brent Dax wrote:
# If foo is an unprototyped function (and thus takes a list in
# P0) we can
# immediately push the values of those calculations on to the list,
# something like (in a lame pseudo-assembler that doesn't use the right
# names
. In the future, this may replace OISC.
from http://www.tuxedo.org/~esr/retro/
:^)
--Brent Dax
[EMAIL PROTECTED]
...and if the answers are inadequate, the pumpqueen will be overthrown
in a bloody coup by programmers flinging dead Java programs over the
walls with a trebuchet.
yourself.
Sorry.
--Brent Dax
[EMAIL PROTECTED]
...and if the answers are inadequate, the pumpqueen will be overthrown
in a bloody coup by programmers flinging dead Java programs over the
walls with a trebuchet.
~~~
#!/usr/bin/perl -w
#we want -w on
#Configure.pl, written by Brent Dax
use
Simon Cozens:
# On Tue, Sep 11, 2001 at 02:22:13AM -0700, Brent Dax wrote:
# A simple autogenerate what's already in Parrot's config.h is easy
#
# This is a good start.
#
# --I've already written a prototype (pasted after my sig)--but
# seems like it's too easy considering what you're talking
of uninitialized value at assembler.pl line 81'
messages...
--Brent Dax
[EMAIL PROTECTED]
...and if the answers are inadequate, the pumpqueen will be overthrown in a bloody
coup by programmers flinging dead Java programs over the walls with a trebuchet.
.pasm missing from the CVS repository?
Check the t/ directory.
--Brent Dax
[EMAIL PROTECTED]
...and if the answers are inadequate, the pumpqueen will be overthrown
in a bloody coup by programmers flinging dead Java programs over the
walls with a trebuchet.
Dan Sugalski:
...
# The jump ops will be easy to figure--either they'll take a
# register, a
# constant number, or a label. We don't allow labels that could
# be confused
# with registers. (No I0: anywhere...)
Noo! How will I write really confusing JAPHs now? :^)
--Brent Dax
[EMAIL
that handles
# converting to native machine code will need to do some analysis and
# register renaming anyway. It can handle putting things in the
# right places.
I seem to remember reading in an article somewhere that Itanium has 128
registers.
--Brent Dax
[EMAIL PROTECTED]
...and if the answers
get the same die-at-compile-time behavior.
In other words, I want exceptions thrown at compile-time to be catchable
at run-time by surrounding try blocks. Are there any barriers to this
working? If so, what are they?
--Brent Dax
[EMAIL PROTECTED]
They *will* pay for what they've done.
.
Okay, we're done!
You can now use `make test_prog' (or your platform's equivalent to
`make')
to build your Parrot.
Happy Hacking,
The Parrot Team
--Brent Dax
[EMAIL PROTECTED]
They *will* pay for what they've done.
H.Merijn Brand:
# I've waited till either Configure or make would do
Damien Neil:
# On Sat, Sep 15, 2001 at 01:15:57AM -0700, Brent Dax wrote:
# As for the 5.6 thing...I think we're supposed to support 5.005 and
# above. Can you tell what Parrot::Opcode needs it for?
# (And if it's for
# 'our', I'm going to punch someone... :^) )
#
# Er...I think
)
# got: 'can't stat t/op/basic1.pbc, code 2
'
# expected: '42'
# Looks like you failed 1 tests of 2.
...
It looks like the backslashes in the path are being interpreted
incorrectly. I don't think the problem is in Configure; can somebody
look at it?
--Brent Dax
[EMAIL PROTECTED
Andy Dougherty:
# On Wed, 19 Sep 2001, Brent Dax wrote:
#
# Andy Dougherty:
# ...
# # +prompt(And what is sizeof(iv)?, 'ivsize');
# # prompt(And your floats?, 'nv');
# # +prompt(And what is sizeof(nv)?, 'nvsize');
# ...
#
# Somehow, this seems like something we ought to be able to do
flags in the wrong place. Most of the other
changes were things like formatting. Patch attached. I'll commit this
myself if nobody has any objections. (Once this is committed, I'll work
on the parrot/config.h stuff, and merge that in to this patch.)
--Brent Dax
[EMAIL PROTECTED]
They *will* pay
Brent Dax:
# Mattia Barbon:
# # ## +#if defined(WIN32)
# # ## +program_code = malloc( file_stat.st_size );
# # ## +#else
# #
# # #Should we be using malloc, or are we supposed to use our
# # own allocator?
# # #(I haven't been munging in the C, so I don't really
# # know--it just looks
like:
printf(%d/%d, sizeof(${iv}), sizeof(${nv}));
in it, and then parse the output? I don't like asking users stuff like
their int sizes--too prone to confusion and mistyping.
--Brent Dax
[EMAIL PROTECTED]
They *will* pay for what they've done.
supposed to use our own allocator?
(I haven't been munging in the C, so I don't really know--it just looks
a little suspicious.)
--Brent Dax
[EMAIL PROTECTED]
They *will* pay for what they've done.
in Parrot is one too. The .pl makes people realize
it's a Perl script; if we used .plx, some people might not understand
what that was. (I can't really speak for the other scripts; Configure
is my specialty.) Besides, ActivePerl on Win32 sets up file
associations on .pl, not .plx. :^)
--Brent
(and maybe double-check the
MANIFEST and MANIFEST.SKIP changes) before it's applied.
--Brent Dax
[EMAIL PROTECTED]
They *will* pay for what they've done.
Simon Cozens:
# On Tue, Sep 18, 2001 at 02:32:32PM -0700, Brent Dax wrote:
# If somebody codes up the alternate dispatch, I can easily modify
# Configure.pl, config_h.in and the hints files to handle it.
# Something
# like this, perhaps:
#
# Something like that, but the Right Way would
Brent Dax:
# Sent: Thursday, September 13, 2001 14:17
# To: Simon Cozens; [EMAIL PROTECTED]
# Subject: RE: Things we need to do.
#
#
# Simon Cozens:
# # 2) Extend the Configure.pl system to autogenerate the
# #Makefile as well. Use Makefile.in as a template, and
# #fill
that this patch *replaces* my last patch, sent earlier today. Do
*not* apply my last patch--apply this one instead.
--Brent Dax
[EMAIL PROTECTED]
They *will* pay for what they've done.
--- c:\old_parrot\Configure.pl Tue Sep 11 02:44:00 2001
+++ Configure.plThu Sep 13 23:32:26 2001
@@ -1,11
I should have that ready in a bit. ITMT, don't apply my other
patches--the next one will cover all of this.
--Brent Dax
[EMAIL PROTECTED]
They *will* pay for what they've done.
# -Original Message-
# From: Simon Cozens [mailto:[EMAIL PROTECTED]]
# Sent: Friday, September 14, 2001 01
Simon Cozens:
# Yeah, that was it! Brent, do you want to take care of that.
# (config_h.in would be better, since it gets mindshare from the
# current Perl 5 build process.)
Didn't take long--patch below sig. You'll also have to rename
config.h.in to config_h.in yourself.
--Brent Dax
[EMAIL
= $Config{ccflags}. -I..,
libs = $Config{libs}
);
:^)
As you can see, I also put in a note in the future for others who can't
find the right place to set defaults, as well as an XXX involving
whether we should 'inherit' ccflags at all.
--Brent Dax
[EMAIL PROTECTED]
They *will* pay
structure in a tarball first, and
send it to myself and anyone else who's interested in this so we can
check it before you commit. This is a large change in the layout; there
are a thousand subtle ways to mess up without noticing it immediately.
Many eyes make bugs shallow, right? :^)
--Brent Dax
Simon Cozens:
# On Tue, Sep 18, 2001 at 02:51:35PM -0700, Brent Dax wrote:
# So, something more like this?
#
# Urh, how can I put this? No.
#
# I *really* want to avoid macro hackery - undef'ing this and
# then testing if it's defined and then redefining it, and
# urgh, urgh, urgh. No.
#
# I
to check for mmap availability.
Configure sets up a bunch of HAS_HEADER_FOO macros in parrot/config.h,
including HAS_HEADER_MEMORY (undef on my Win32 system). Would this be
the correct file?
--Brent Dax
[EMAIL PROTECTED]
They *will* pay for what they've done.
Brent Dax:
# Okay, here's the results of my lame imitation of smoke
# testing--a script
# (highly customized for my machine) called autotest.
Here's the results of a run on FreeBSD. It looks like something is
broken in the integer test. (It's not my script--I get the same errors
when I run
string.o strnative.o test_main.o
#
# Definitely bugs in Configure there; cc has to be used as the
# linker or -lc
# isn't added (and possibly some of the other crt.o files too), and
# libraries have to be after all the object files.
I've already patched Makefile.in to fix this.
--Brent Dax
[EMAIL
things together. It spits out a crapload of debugging
information--symbol table dumps and stack dumps--but it's all on STDERR
so you can redirect that to your null device to get rid of it.
Share and enjoy!
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've
Dan Sugalski:
# (I'll start
# stuffing 0xDEADBEEF in there if I have to... :)
Actually, I think 0xDECAF would bug late-night coders even more! :^)
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
FreeBSD/x86
OK/OK
Win32/x86
OK/NOK (report after my sig)
Linux/IA64
OK/NOK (smoke report after my sig)
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
Win32/x86:
Failed Test Stat Wstat Total Fail Failed List of Failed
Mattia Barbon:
# Makes Win32 use ExtUtils::Command::rm_f as a rm -f replacemnt.
Thanks, applied. This one's been hovering near the top of my stack for
a while, but I kept pushing new things on above it till now.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay
Automated snapshots and e-mail notifications of CVS commits have both
stopped. What's going on?
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
# inclusion of a
# definition of NULL (whatever that might mean).
What's the semantic difference between NULL and undef?
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
I'm back. I notified Simon on the tenth that I was going to be away
until today. I'm trying to catch up on the nine-hundred-odd messages
the p6? and p5p have thrown at me, so I may be realistically out of
commission for a couple days more.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking
. That is just too scary. I am not touching that with a ten-foot
pole. Sorry.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, Im not going to fire a $2 million missile at a $10
empty tent and hit a camel in the butt.
--Dubya
don't get what this is even used for.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, I'm not going to fire a $2 million missile at a $10
empty tent and hit a camel in the butt.
--Dubya
Dan Sugalski:
# At 10:20 PM 10/24/2001 +0100, Simon Cozens wrote:
# On Wed, Oct 24, 2001 at 01:56:01PM -0700, Brent Dax wrote:
# core_ops.obj : error LNK2019: unresolved external
# symbol _sleep
# referenced in function _Parrot_sleep_i
# test_prog.exe : fatal error LNK1120: 1
the
placement of 'type'.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, Im not going to fire a $2 million missile at a $10
empty tent and hit a camel in the butt.
--Dubya
*BabyPerl is a program I'm working on which converts a subset of Perl 6
into bytecode
, I'm getting this headers thing too, from all @perl.org mailing
lists--not just p5p. Ask, is this your department, and if so can you
fix it?
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, Im not going to fire a $2 million missile at a $10
empty tent and hit
Damian Conway:
# BTW, colon isn't an operator (it's a separator), so it can't be hyped.
What do you mean? We can hype the colon all we want! :^)
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, Im not going to fire a $2 million missile at a $10
empty tent
to stabilize
# this anomoly before it destroys Perl 6.
All these Star Trek references are threatening to make my warp core
breach... :^)
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, Im not going to fire a $2 million missile at a $10
empty tent and hit a camel
and add re.h (defines data structures and such)
and t/op/re.t (six tests). All tests, including the new ones, pass.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, Im not going to fire a $2 million missile at a $10
empty tent and hit a camel in the butt.
--Dubya
stack_depth(interp, mystack-base);
}
/* etc. */
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, Im not going to fire a $2 million missile at a $10
empty tent and hit a camel in the butt.
--Dubya
Richard J Cox:
# Firstly, 8am code this morning builds on Win32 without
# problem, other than
# configure.pl not knowing that link is the linker (which
# appears to be down
# to ActiveState not knowing).
Does it have to know? If so, set it in the hints file
(hints/mswin32.pl).
--Brent Dax
Dan Sugalski:
# At 09:37 AM 10/24/2001 -0700, Brent Dax wrote:
# It's probably a problem. Configure.pl creates a macro
# HAS_HEADER_SYSTIME in config.h--why isn't Parrot respecting it?
#
# Parrot bug. I'll go fix unless someone beats me to it.
Patch below my sig fixes this; however, after
to leave. I'll work on this more later.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, I'm not going to fire a $2 million missile at a $10
empty tent and hit a camel in the butt.
--Dubya
don't want to bother to fix.
(classes\intclass.c(16) : warning C4716: 'Parrot_int_type' : must
return a value and such.) Other than that, though, it works fine.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, Im not going to fire a $2 million missile at a $10
empty
related to this: is
INTVAL (and thus the I registers) supposed to be big enough to hold a
pointer?
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, I'm not going to fire a $2 million missile at a $10
empty tent and hit a camel in the butt.
--Dubya
for a Parrot compiler are often easier to
deal with then trying to implement a specific algorithm in assembler.
(Probably because Parrot is a pretty high-level sort of assembler.)
Whatever you do, have fun, and Happy Hacking!
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action
. :^)
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, I'm not going to fire a $2 million missile at a $10
empty tent and hit a camel in the butt.
--Dubya
.)
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, I'm not going to fire a $2 million missile at a $10
empty tent and hit a camel in the butt.
--Dubya
The patch attached is courtesy of Richard J. Cox. It fixes the VC++
warnings about functions declared to return a value but not actually
returning one. I'll apply it in a couple hours if there aren't any
objections.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take
of a string) into an integer
# register, but if we don't we should.
Have you looked at the regexp patch I posted last night? It's pretty
much functional, including reOneof. Still, these could be useful
internal functions... *ponder*
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I
Dan Sugalski:
# At 10:36 PM 11/3/2001 -0800, Brent Dax wrote:
# Well, for now we're using Perl for Configure, but that won't
# be possible
# in the final version. Nasty bootsrapping issues with that. :^)
#
# You'd be surprised... :)
#
# Seriously, miniparrot, enough to do simple file ops, spawn
()?
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, I'm not going to fire a $2 million missile at a $10
empty tent and hit a camel in the butt.
--Dubya
reFinished
$backb:
rePopindex $backa
branch $findxb
$backa:
rePopindex $advance
branch $findany
$fail:
set I0, 0
reFinished
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
When I take action, Im not going to fire a $2 million missile
1 - 100 of 829 matches
Mail list logo
