27; or major changes to
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...
tested, but you get the idea...
Or, a slightly different syntax from yours:
schwartzian {
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. :)
W
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.
--Brent Dax
Excuse typos, it's hahd to write on a Palm...
-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 th
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=unq
[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
y in the
>various linkers, which is a Bad
>Thing.
Why don't we just say, "Variables and functions will NOT have the same
post-prefix 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...
.
How about $a cat $b? That keeps the theme of strings using words and
numbers using symbols--like eq vs. ==.
--Brent Dax
... (cue X-Files 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]
essed?) references, and
concat otherwise.
Does any of that make sense? Or should I be returned to my straightjacket?
:^)
--Brent Dax
[EMAIL PROTECTED]
ays "remember my old value whenever I'm
assigned to." We'll call this 'undoable'. In this case:
@a is undoable; #@a=() is noticed, @a[0] isn't
@a are undoable;#@a[0] is noticed, @a=() isn't (or maybe it is?)
#i could have used has/have instead, but is/are makes more sense here
--Brent Dax
[EMAIL PROTECTED]
sub bar is property(variable) { #property that attaches to the variable
...
}
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 C
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)
>
has exactly one meaning,
regardless of context. It also gives () back its C meaning, grouping stuff
together so it'll be evaluated first, instead of a meaning that can be
different in different contexts. (In general, I think that "syntactic
operators" like parenthesis and comma shoul
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 ex
5
print "Baz: $(Baz('a', 'b'))"; #prints Baz: b
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]
o -language. :^) )
BTW, one other random thought I came up 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]
nse in any computer language. You may have 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]
et me know.)
Thanks,
--Brent Dax
[EMAIL PROTECTED]
27;d have to turn it on explicitly.
Could we use this so that we don't have to use 'ref' (or its moral
equivalent) in method lookups? In other words, if $spot is declared to
hold a Dog, can we assume that it does, thus skipping the check with
'ref' normally used for method dispatch? Would this even buy us
anything? Why am I asking myself these questions? Why are the
orderlies putting me in a white truck?
--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 &
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]
rating op wrappers around
# vtable functions,
# (saving one 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]
od example of a bad use of is-a. It also meant that the class
was nearly 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]
to
the uninitiated.
--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."
eds to know things like 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."
$AUTOLOAD is in.)
The second step takes care of resolving the address of the function; it
handles picking which (if any) 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 amu
ity of a symbol table through
the MY:: pseudo-package.
Once again, why isn't MY:: stored in some sort of anonymous symbol
table? This would allow us to do all the things we can normally do with
a global, without the hassles of writing a magical pseudo-package.
--Brent Dax
[EMAIL PROTECTED]
/-no--"foo"-\
opt: FOO redefined? -< >---print
\-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
# -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 detect
# -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 r
# -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
# -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) co
# -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
o in a specific language's string
# PMC vtables?
Perl *scalars* are PMCs. Those PMCs may hold strings within them.
However, 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 f
# -Original Message-
# From: Dan Sugalski [mailto:[EMAIL PROTECTED]]
# Sent: Monday, September 03, 2001 4:31 PM
# To: Ken Fox; Brent Dax
# Cc: Simon Cozens; [EMAIL PROTECTED]
# Subject: Re: Should MY:: be a real symbol table?
#
# >Lexicals are fundamentally different from Perl's
# -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]]
# Se
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 th
do-assembler that doesn't use the right
names for instructions):
load $x, I1
load 1, I2
add I1, I2, I3
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) tha
izer 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 righ
|threeq 34|
|... |
Now, on a call like substr($str, 36, 1) we can skip all the way to byte
34--which we know represents character number 33--and count from there.
--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."
rograms in the OISC machine language are included.
We now have available have a revised and expanded version of oisc called
OIC. 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."
o I don't have the tools to make a diff (I'm trying to
get PPT working) so you'll have to turn it into a patch 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 Ja
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&
k on the FreeBSD box I have access to. Now to figure out
what's causing all those 'use 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."
n is spread across three
# > different files.
#
# Oops--that breaks the assembler. This patch fixes the assembler to
# work with the prior patch.
That explains it! :^)
--Brent Dax
[EMAIL PROTECTED]
"...and if the answers are inadequate, the pumpqueen will be overthrown in a bloody
coup by program
nd
# test2.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
t I know of, so the bit 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 PRO
e is in a try block;
otherwise we 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.
very
own Makefile, config.h, and Parrot::Config to disk.
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
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 someon
at line 74)
# 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
DOD and aggressive_DOD or something
# along those lines, if we wanted.
I could imagine a few pathological cases that would invoke two DOD runs
before we get around to anchoring the original header to the root set.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} q
b(); /* The macros don't really need a Parrot_ prefix, do
they? */
Str_params_3(a, b, c);
Decl_str(d); /* These aren't needed anymore, actually... */
Decl_str(e);
Return(
string_concat(
string_concat(a, b),
c
)
);
uming that C++'s try and catch can take statements instead of
blocks, anyway--although even if they don't, it's just four more
characters.)
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
blink: Text blinks (alternates between visible and invisible).
Conforming user agents are not required to support this value.
--The W3C CSS-2 Specification
kes sense to me.
I'm sure it's still there. Otherwise there's no way to take a reference
to a scalar.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
blink: Text blinks (alternates between visible and invisible).
Conformin
Jeff:
# I haven't been tracking assembly speed at all. Keep in mind
# that a perl assembler is only a temporary measure, and it'll
# be rewritten in C eventually. It's only written in Perl so
C or PASM (or Perl 6)? The latter might be better.
--Brent Dax <[EMAIL PROT
fdefs. :^)
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
blink: Text blinks (alternates between visible and invisible).
Conforming user agents are not required to support this value.
--The W3C CSS-2 Specification
d KEY structures, not strings.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
blink: Text blinks (alternates between visible and invisible).
Conforming user agents are not required to support this value.
--The W3C CSS-2 Specification
in Parrot. Unfortunately, that
means grepping over the core to change it, but that'll have to happen
anyway.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
blink: Text blinks (alternates between visible and invisible).
Conforming user agents a
.dll instead of a .so on Windows when the
..so is hardcoded in?
-callnative is the wrong way to do it. What we need is a subroutine
PMC and a call vtable method.
However, this isn't a bad start. Overall, Melvin++.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_&q
Leon Brocard:
# This little patchette lets the new shiny assembler cope with
# using an I register as a PMC key, eg "P14[I3]". Obviously
# brainf*ck needs to be in the testsuite ;-)
See my comment on a previous, similar patch by Simon Glover.
--Brent Dax <[EMAIL PROTECTED
t ask questions by default. You can tell it to ask
questions by passing in the "--ask" switch on the command line. You can
also tell it the linker's name directly by passing in
"--ld=(linker-name)".
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"}
.
In that case, I have a half-written, untested bison/flex parser
attached. Have the appropriate amount of fun.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
blink: Text blinks (alternates between visible and invisible).
Conforming user
all round.
Just because we're trying to make radical changes doesn't mean we can't
make a small sacrifice to the backwards-compatibility gods. After all,
it would be kinda nice if there were users besides p6* list members, and
I doubt it'll work without at least the small sacrifi
ones, obviously).
#
# There. Nearly 3% of the CPAN ported in two fell swoops! ;-)
Why bother? You've already put P::RD and T::B effectively in the core!
;^)
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
blink: Text blinks (alternat
nterpreted the same way, but typed a bit differently. It won't
match your regex.
The moral of the story is that you should not try to parse the *MLs with
regexen--use modules instead.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure
\{ \}
| \< !? [ \w+ | \d+ , \d+ ] \>
)
}
}
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
Early in the series, Patrick Stewart came up to us and asked how warp
drive worked. We explained some of the hypothetical principles
Larry Wall:
# On Fri, 7 Jun 2002, Damian Conway wrote:
#
# > Brent Dax wrote:
# >
# > > grammar Perl6::Regex {
# > > rule metachar { <[<{(\[\])}>:*+?\\|]>}
# > >
# > > rule ws { [<[\h\v]>|\#\N*]*
Subject says it all. Updates conventions to be consistent with much of
the core. Unfortunately, that doesn't include 'struct Parrot_Interp'.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
Early in the series, Patrick
David M. Lloyd:
# NOTE: DO NOT APPLY THIS PATCH TO PARROT unless you like the
# smell of platforms burning. :-)
Er, what patch?
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
Early in the series, Patrick Stewart came up to us and aske
David M. Lloyd:
# On Fri, 7 Jun 2002, Brent Dax wrote:
#
# > Er, what patch?
#
# It was attached because it is 214K. I could resend with it
# inline if nobody minds the large message body.
I don't think anybody minds an attached patch, but I didn't get the
attachment.
--Bren
David M. Lloyd:
# On Fri, 7 Jun 2002, Brent Dax wrote:
#
# > David M. Lloyd:
# > # On Fri, 7 Jun 2002, Brent Dax wrote:
# > #
# > # > Er, what patch?
# > #
# > # It was attached because it is 214K. I could resend with
# it # inline
# > if nobody minds the large messa
hat we wrap mmap and munmap in
something. I think Windows has similar functionality through a
different API, so Parrot_map and Parrot_unmap might be in order.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
Early in the series, Patrick Stew
[EMAIL PROTECTED]:
# At 21:51 on 06/07/2002 PDT, "Brent Dax" <[EMAIL PROTECTED]> wrote:
#
# > # Of these, 2 are not defined by ANSI C89:
# > # read (in core_ops.o,core_ops_prederef.o)
# > # write (in core_ops.o,core_ops_prederef.o)
# > #=20
# > # Prett
27;re assuming a minimum C89 level of ANSI
# > compiler compliance.
#
# hosted, or freestanding?
Hosted. Freestanding isn't complete enough to do anything with--you
don't even have file I/O. Besides, you'll most likely be
cross-compiling for WinCE.
--Brent Dax <[EMAIL PROTECTED]&
mplementing their interpreters in Perl... ;^)
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
Early in the series, Patrick Stewart came up to us and asked how warp
drive worked. We explained some of the hypothetical principles . . .
&qu
next>/ && $best &&
# $0.length < $best.length {
# }
# fail unless $best;
# let $0 := $best;
# .pos = $best.pos;
# }}
#
# then:
#
# "bacamus" =~ / /;
Will that handle captures correctly? Maybe you should temporiz
er a valid delimiter, and if you want a balanced
one '[' is usually ideal.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
Early in the series, Patrick Stewart came up to us and asked how warp
drive worked. We explained
tation language) and a willingness to dig
# through the Apocalypses and Exegeses. (Well, that and not minding the
# first version likely getting tossed out when we do the final
# implementation... :)
If we can use a real parser (Parse::Yapp, Parse::RecDescent), I'd love
to help. If not...we
otenuse is shorter. And all
# we're actually interested in which one is shorter, aren't we?)
Assuming x and y are integers, yes. Which'll probably be all we ever
deal with, so for all intents and purposes you're correct.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {&quo
some reason. Ask Simon if you really want to
know.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
He who fights and runs away wasted valuable running time with the
fighting.
et the
replacement string), but I changed my mind. Apparently that never
disappeared.
Overall, well done on the file--I think you explained bitmaps better
than I could have. :^)
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
He who fights and runs away wasted valuable running time with the
fighting.
John Porter:
# Brent Dax wrote:
# > > 2. What does having a Parrot_ prefix signify, considering
# > > both the opcodes and the embed api use it?
# >
# > It signifies one of the following:
# > -This function is externally visible.
# > -This function belongs to Parr
g and namespace
# management in general.
I'd be happy to draw up guidelines if someone can tell me what they
should cover (naming of functions and data structures--anything else?)
and if people will read and review when I've finished it.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {&quo
Ashley Winters:
# On Monday 15 July 2002 02:25 am, Brent Dax wrote:
# > -C library wrappers: This is Parrot's version of the
# function, so it
# > makes sense to prefix it with Parrot_.
# >
# > The third category I can see having a prefix of plat_ (for
# platform)
# &g
and converting those that only
contain pairs.)
# (I hope the answer isn't "white space" . . )
#
#
# [Hi, I'm new around here, so I'll give you the three-line
# introduction. I teach Perl at Monash Uni, my office is in the
# same corridor as Damian's, and I like cats, chocolate, and
# curry. (Not all at once.) ]
Well, any friend of Damian's... :^)
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
He who fights and runs away wasted valuable running time with the
fighting.
John Porter:
# Brent Dax wrote:
# > Ashley Winters:
# > > c. parrot_sprintf
# >
# > Lowercase is always the hallmark of struct names, i.e.
# > parrot_string_t.
#
# Ehhh... you yourself said something about plat_ and misc_
# as (theoretical) alternatives.
#
# Anyway, it'
xt() keyword would be like the opposite of want(). Of course,
something like:
context $x: foo();
Might not work.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
He who fights and runs away wasted valuable running time with the
fighting.
Paul Kienzle:
# On Mon, Jul 15, 2002 at 02:26:55AM +, Ashley Winters wrote:
# > On Monday 15 July 2002 02:25 am, Brent Dax wrote:
# > > -C library wrappers: This is Parrot's version of the
# function, so
# > > it makes sense to prefix it with Parrot_.
# > >
# &g
ectorization happens, and with the ability to
# define your
# > own array behavior, you can pretty much do this however you
# want anyway.
#
# Yes but it would be nuts to have PDL arrays do things one way
# and inbuilt
# compact arrays do things another way.
No, it wouldn't. PDL is
s.
Autodereferencing happens whenever we have a scalar but we need an array
or hash; autoreferencing happens whenever we have an array or hash but
need a scalar (usually because of scalar assignment, but not
necessarily).
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
He who fights and runs away wasted valuable running time with the
fighting.
David Whipp:
# Brent Dax wrote:
# > $href = hash { %hash }; #B
#
# Why the curlies? if C is a function (ctor), then surely
# these should be parentheses. In this context, parentheses are
# optional, so this could be written
#
#$href = hash %hash;
C is not a function. It&
es in text. :^) ) Reading
this, I noticed a potential problem in :w.
To put it simply, what do these expand to?
m:w/foo [~|bar]/
m:w/[~|bar] foo/
m:w/[~|bar] [^|baz]/
m:w/@foo @bar/
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding
t.t
# languages/regex/test.pl
# +languages/scheme/Makefile.in <-- should be gone
# languages/scheme/Scheme.pm
# languages/scheme/Scheme/Generator.pm
# languages/scheme/Scheme/Parser.pm
# @@ -393,6 +424,7 @@
# resources.c
# runops_cores.c
# rx.c
# +rx.dev
# rx.ops
# rxstacks.c
# stac
1 - 100 of 891 matches
Mail list logo
