On Tue, Apr 20, 2004 at 03:53:31PM -0400, Aaron Sherman wrote:
: In specific, here is a proposal for execution:
:
: multi run(string $command) returns(Process) {...} # Funky shell default
: multi run(Process $process) returns(Process) {...} # Relies on $process.cmdline
Eh? What does
On Tue, Apr 20, 2004 at 02:16:01PM -0400, Aaron Sherman wrote:
: Well, I have a lot to digest, but off the top of my head (and having
: nothing to do with objects, but rather the string discussion at the
: end), it would be very useful if I could assert:
:
: no string "complex";
:
: or some
The attached patch adds 2 Configure.pl options, to help with the
process of getting ICU to build on platforms which are having
difficulties with it:
% perl Configure.pl --help
...
ICU Options:
--icuplatform=(platform) Platform name to pass to ICU's
runConfigureICU
--icuconfigureargs=(ar
On 20 Apr 2004, at 12:53, Dan Sugalski wrote:
So, parrotcode.org's getting a bit crusty in its content (though with
a spiffy-keen new look if you've not looked in a while) and we need to
fix that.
Agreed -- as an effective newcomer to the project (followed it for a
while a year or so ago, but
Aaron Sherman <[EMAIL PROTECTED]> wrote:
> Why does Parrot need this? What's so special about hyper operations that
> makes Parrot want to take them on?
The special thing is optimizing for integers and floats. The bad thing
is overridden »op« for aggregates holding PMCs. These might do whatever
t
On Tue, Apr 20, 2004 at 10:25:04PM +0200, Juerd wrote:
> Brent 'Dax' Royal-Gordon skribis 2004-04-20 12:58 (-0700):
> > method buffersize()
> > will store {
> > my $sqrt=$^v.sqrt;
> > die "$^v is not a power of two" unless int($sqrt) == $sqrt;
> > $.b
On Tue, 20 Apr 2004, Juerd wrote:
> Brent 'Dax' Royal-Gordon skribis 2004-04-20 12:58 (-0700):
> > method buffersize()
> > will store {
> > my $sqrt=$^v.sqrt;
> > die "$^v is not a power of two" unless int($sqrt) == $sqrt;
> > $.buffer = "\x[0]" x $^
On Tue, 2004-04-20 at 13:55, Larry Wall wrote:
> Okay, let's put this one to rest.
Good, and I'll not try to speak ill of the dead thread, so ignoring hash
and/or array access, let me respond to the end of your message.
> As for C, it probably needs to be completely rethought anyway,
> along wit
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 8:10 PM +0200 4/20/04, Leopold Toetsch wrote:
[ unused scalar vtables in aggregates ]
>>Aren't the relevant vtable slots for aggregates unused anyway?
> Only because we've not gotten around to writing the code. :)
Do you want to reserve these just fo
On Tue, 20 Apr 2004, Brent 'Dax' Royal-Gordon wrote:
> John Williams wrote:
> > I'm not saying there is anything wrong with that, but John Siracusa is
> > asking for something different, I think. A simple accessor which looks
> > like a method without having to play with Proxy, FETCH, STORE, etc.
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Something for people to work on, and something that can be worked on
> piecemeal (which is good). We need to make parrot's build less
> dependent on the flags set in the current perl install, especially
> for things like the C compiler and linker flags.
..
On Tue, 2004-04-20 at 16:30, Dan Sugalski wrote:
> Because they can be overridden separately from the regular version of
> the operation.
Of course.
Quoting A3 (note, syntax has changed, but as far as I know, the content has not):
@a ^* @b
is equivalent to this:
Brent 'Dax' Royal-Gordon skribis 2004-04-20 12:58 (-0700):
> method buffersize()
> will store {
> my $sqrt=$^v.sqrt;
> die "$^v is not a power of two" unless int($sqrt) == $sqrt;
> $.buffer = "\x[0]" x $^v;
> }
> { +$.buffer.bytes }
Could
At 4:20 PM -0400 4/20/04, Aaron Sherman wrote:
On Tue, 2004-04-20 at 11:53, Dan Sugalski wrote:
Y'know... let's just go all the way with this, since we're going to have to.
We'll add a hyper version of all the vtable entries.
Another of those darned "I don't get it" posts, but I'll keep this on
On Tue, 2004-04-20 at 1:26PM, Aaron Sherman wrote:
>
> Another of those darned "I don't get it" posts, but I'll keep
> this one short.
>
> Why does Parrot need this? What's so special about hyper
> operations that makes Parrot want to take them on?
I'm not sure I entirely get it myself, but perhap
On Tue, 2004-04-20 at 11:53, Dan Sugalski wrote:
> Y'know... let's just go all the way with this, since we're going to have to.
>
> We'll add a hyper version of all the vtable entries.
Another of those darned "I don't get it" posts, but I'll keep this one
short.
Why does Parrot need this? What'
On 4/20/04 4:08 PM, Aaron Sherman wrote:
> On Tue, 2004-04-20 at 15:40, John Siracusa wrote:
>> On 4/20/04 2:37 PM, Larry Wall wrote:
>>> It's wrong to introduce a fundamental asymmetry that breaks the contract
>>> that an accessor can be used as a variable.
>>
>> Er, I think we have different def
John Williams wrote:
class Dog {
has $.foo
will FETCH { ... }
will STORE { ... }
;
}
I'm not saying there is anything wrong with that, but John Siracusa is
asking for something different, I think. A simple accessor which looks
like a method without h
On Tue, 2004-04-20 at 15:40, John Siracusa wrote:
> On 4/20/04 2:37 PM, Larry Wall wrote:
> > It's wrong to introduce a fundamental asymmetry that breaks the contract that
> > an accessor can be used as a variable.
>
> Er, I think we have different definitions of "accessor." I'm perfectly
> happy
Something for people to work on, and something that can be worked on
piecemeal (which is good). We need to make parrot's build less
dependent on the flags set in the current perl install, especially
for things like the C compiler and linker flags.
So... if folks would like to take a shot, any a
On 2004-04-20 at 11:37:18, Larry Wall wrote:
> So do whatever you like to the declarations, but make sure you preserve
> the symmetry and extensibility of
>
> $obj.foo([EMAIL PROTECTED], *%NONSENSE) # get value of $.foo
> $obj.foo([EMAIL PROTECTED], *%NONSENSE) = 5 # set $
On 4/20/04 2:37 PM, Larry Wall wrote:
> On Tue, Apr 20, 2004 at 01:15:24PM -0400, John Siracusa wrote:
> : With that "has" line alone, you auto-magically get an accessor that works
> : like this:
> :
> : $obj.foo# get value of $.foo
> : $obj.foo(5) # set $.foo = 5
>
> I don't care wha
So, parrotcode.org's getting a bit crusty in its content (though with
a spiffy-keen new look if you've not looked in a while) and we need
to fix that.
Rather than putting this on my essentially infinitely long todo list,
this'd be a good spot for someone who wants to get involved to, well,
get
Joseph E. Sacco <[EMAIL PROTECTED]> wrote:
> ...
> t/pmc/signal# Failed test (t/pmc/signal.t at line 65)
The problem is very likely in the test itself. To verify that you could
run e.g. the first test[1] with a longer sleep and send a SIGHUP
Jeff Clites <[EMAIL PROTECTED]> wrote:
> Here's another tiny patch, to let us fast-fail string_equal if we have
> cached hashval's which don't match.
What about a hash value collision?
leo
On Tue, Apr 20, 2004 at 01:15:24PM -0400, John Siracusa wrote:
: With that "has" line alone, you auto-magically get an accessor that works
: like this:
:
: $obj.foo# get value of $.foo
: $obj.foo(5) # set $.foo = 5
I don't care what syntactic sugar you put underneath, but if you expos
At 8:10 PM +0200 4/20/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
We'll add a hyper version of all the vtable entries. Since this is
going to bloat the hell out of the vtable, we'll do it by adding a
VTABLE *hyper to the main vtable structure and hang it off there.
Aren't
The Perl 6 Summary for the fortnight ending 2004-04-18
The only problem with summarizing two week's worth of Perl 6 happenings
is that there's twice as much stuff to summarize. Still, there's no way
I could have made the time to write a summary last week so I'll take my
lumps. I am
Well, I have a lot to digest, but off the top of my head (and having
nothing to do with objects, but rather the string discussion at the
end), it would be very useful if I could assert:
no string "complex";
or something like that. That is to say, I would love to have a way to
say that my
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> We'll add a hyper version of all the vtable entries. Since this is
> going to bloat the hell out of the vtable, we'll do it by adding a
> VTABLE *hyper to the main vtable structure and hang it off there.
Aren't the relevant vtable slots for aggregates unu
On Tue, 20 Apr 2004, Luke Palmer wrote:
> John Williams writes:
> > On Tue, 20 Apr 2004, Luke Palmer wrote:
> > > There. Now here's the important part: in order to *use* all this, you
> > > import whatever module defines it, and then say:
> > >
> > > class Dog {
> > > method foo (?$ar
Okay, let's put this one to rest. I've suspended judgement long enough.
Let me first say that I have my own personal biases, and they are
towards keeping things visually and psychologically distinctive,
rather than towards reducing keystrokes. (Though I have enough
arthritis in my hands to at le
On Apr 19, 2004, at 2:25 AM, Leopold Toetsch wrote:
Jeff Clites <[EMAIL PROTECTED]> wrote:
This change speeds up the attached benchmark by a factor of 1.86 in
the
optimize case (via --optimize, so -Os), or 3.73 in the unoptimized
case
(on Mac OS X):
Wheee, that's a lot.
Here's another tiny patc
On 4/20/04 12:14 PM, Luke Palmer wrote:
> Okay, well, I thought that my example did that, but apparently using
> C and C is a little too complex... (my sentiments
> are beginning to follow Larry's, in that I'm not sure you know what you
> want -- perhaps you could give a hypotheical syntax?)
There
On 2004-04-20 at 10:51:47, Luke Palmer wrote:
> I guess I bogged down that message with the implementation, so the
> result may have been easy to miss.
That is what happened in my case. Apologies; it looks like your
original solution would do the job nicely. As long as the requisite
module come
John Williams writes:
> On Tue, 20 Apr 2004, Luke Palmer wrote:
> > There. Now here's the important part: in order to *use* all this, you
> > import whatever module defines it, and then say:
> >
> > class Dog {
> > method foo (?$arg) is accessor {
> > # accessor code here
>
On Tue, 20 Apr 2004, Luke Palmer wrote:
> There. Now here's the important part: in order to *use* all this, you
> import whatever module defines it, and then say:
>
> class Dog {
> method foo (?$arg) is accessor {
> # accessor code here
> }
> }
>
> If that's not
Juerd writes:
> Peter Haworth skribis 2004-04-20 14:56 (+0100):
> > > I think %hash<> is best explained as %hash{ << key key
> > > key >> } with implicit curlies, not as an alternative to curlies.
> > In that case, why aren't you suggesting something more in line with that?
> > Here's what I'd lik
Austin Hastings writes:
> One of the things that got a little less clear with A12 was the idea of
> multiple C clauses.
>
> Once upon a time, we talked about:
>
> my $spot is Dog is const is persistent is ...;
>
> Obviously some of those are traits, now. However, I'm wondering how to
> handle
# New Ticket Created by "Joseph E. Sacco, Ph. D."
# Please include the string: [perl #28995]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=28995 >
System:
* PPC with dual 533MHz G4 CPU's, 1GB RAM, SCSI disks
* Yellow Do
Mark J. Reed writes:
> Let me just chime in with my support for John's basic idea. I would
> definitely prefer that it be easy to arrange things such that
>
> $obj.foo = 'bar'
>
> winds up invoking a method on $obj with 'bar' as an argument, rather
> than invoking a method on $obj that ret
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 8:30 AM +0200 4/20/04, Leopold Toetsch wrote:
>>
>>Why I second table? This just adds duplicate code paths and complexity.
>>One constant table ought to be enough.
> Mainly because I was assuming that we were going to separate the
> float, pmc, and stri
At 4:28 PM +0200 4/20/04, Leopold Toetsch wrote:
I've implemented a (rather hackish and incomplete) new opcode called
C. Usage looks like:
ar = new IntList
ar = 100
hyper
ar = 10
or
hyper
ar += 10
The atached tests fill an integer array with one Meg int constants
and
One of the things that got a little less clear with A12 was the idea of
multiple C clauses.
Once upon a time, we talked about:
my $spot is Dog is const is persistent is ...;
Obviously some of those are traits, now. However, I'm wondering how to
handle things like my recent suggestion of a clas
Jens Rieks <[EMAIL PROTECTED]> wrote:
> What does this do now?
> set Px, "str"
Good question:
$ cat set.pasm
new P0, .PerlString
set P0, "str"
set S0, P0
chopn S0, 2
print "str"
print "\n"
end
$ parrot set.pasm
s
:)
We should separate the 2 cases (set_p_sc and set_p_s)
> -Original Message-
> From: Mark J. Reed [mailto:[EMAIL PROTECTED]
>
> Let me just chime in with my support for John's basic idea. I would
> definitely prefer that it be easy to arrange things such that
>
> $obj.foo = 'bar'
>
> winds up invoking a method on $obj with 'bar' as an a
Mark J. Reed wrote:
Let me just chime in with my support for John's basic idea. I would
definitely prefer that it be easy to arrange things such that
$obj.foo = 'bar'
winds up invoking a method on $obj with 'bar' as an argument, rather
than invoking a method on $obj that returns an lvalue to wh
I've implemented a (rather hackish and incomplete) new opcode called
C. Usage looks like:
ar = new IntList
ar = 100
hyper
ar = 10
or
hyper
ar += 10
The atached tests fill an integer array with one Meg int constants and
then increment each value 5 times.
Here are the
Peter Haworth skribis 2004-04-20 14:56 (+0100):
> > I think %hash<> is best explained as %hash{ << key key
> > key >> } with implicit curlies, not as an alternative to curlies.
> In that case, why aren't you suggesting something more in line with that?
> Here's what I'd like to see instead of your
At 10:51 AM -0400 4/20/04, John Siracusa wrote:
On 4/20/04 10:42 AM, Dan Sugalski wrote:
At 9:50 AM -0400 4/20/04, John Siracusa wrote:
On 4/19/04 7:16 PM, Larry Wall wrote:
Well, no, we're still stuck at run-time validation of that. In the case
of methods you can't really do anything else an
On 4/20/04 10:42 AM, Dan Sugalski wrote:
> At 9:50 AM -0400 4/20/04, John Siracusa wrote:
>> On 4/19/04 7:16 PM, Larry Wall wrote:
>>> Well, no, we're still stuck at run-time validation of that. In the case
>>> of methods you can't really do anything else anyway, generally speaking.
>>
>> Why is
At 8:30 AM +0200 4/20/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
The interpreter stuff's simple enough--we teach the ops preprocessor
to handle them the same way that it does string constants, and index
into the PMC constant table. We'll want to put them in a separate
p
At 9:50 AM -0400 4/20/04, John Siracusa wrote:
On 4/19/04 7:16 PM, Larry Wall wrote:
> Well, no, we're still stuck at run-time validation of that. In the case
of methods you can't really do anything else anyway, generally speaking.
Why is that?
Because at compile time all you have is a generic t
Let me just chime in with my support for John's basic idea. I would
definitely prefer that it be easy to arrange things such that
$obj.foo = 'bar'
winds up invoking a method on $obj with 'bar' as an argument, rather
than invoking a method on $obj that returns an lvalue to which
'bar' is
On Fri, 16 Apr 2004 23:45:48 +0200, Juerd wrote:
> Jonathan Scott Duff skribis 2004-04-16 15:51 (-0500):
> > Except that you've put things in this explanation that shouldn't be
> > there IMHO. The %varname<> is a special case, but not of "getting a
> > single item from a hash", rather it's a specia
On 4/20/04 1:25 AM, Luke Palmer wrote:
> John Siracusa writes:
>> The "will STORE" stuff covers the easy cases, but can I extend it all the
>> way up to a name() that's a multimethod with a ton of optional args? I
>> supposed you can (technically) do all of that with "will STORE", but it
>> seems
On 4/19/04 10:04 PM, Damian Conway wrote:
> John Siracusa wrote:
>> I'd either like a way to more cleanly extend the default accessor's
>> assignment behavior down the road (i.e. by just writing a new name() method,
>> not by hacking away at STORE traits and adding private worker subs) or a way
>>
On 4/19/04 9:05 PM, Damian Conway wrote:
> You want:
>
> sub foo(+$a is required, +$b is required) { ... }
Yes, that would be just fine :)
-John
On 4/19/04 7:20 PM, Larry Wall wrote:
> On Mon, Apr 19, 2004 at 06:53:29PM -0400, John Siracusa wrote:
> : Yeah, that's exactly what I don't want to type over and over :)
>
> I really don't understand what you're getting at here. First you
> complain that you'd rather write an ordinary method, an
On Tuesday 20 April 2004 09:44, Leopold Toetsch wrote:
> set Sx, Sy # alias Sx to Sy
> set Sx, "str" # set Sx to COW copy of "str"
> set Px, Sy # CHANGED make Px refer to Sy
> assign Px, Sy # set Px to COW copy of Sy
What does this do now?
set Px, "str"
jens
On 4/19/04 7:16 PM, Larry Wall wrote:
> On Mon, Apr 19, 2004 at 01:44:53PM -0400, John Siracusa wrote:
> : ...named and required, or named and optional? IOW, is this all true?
> :
> : sub foo(+$a, +$b) { ... }
> :
> : foo(); # compile-time error!
> : foo(1, 2); # compil
Chromatic <[EMAIL PROTECTED]> wrote:
> What's the secret syntax for passing and retriving arrays of things to
> and from NCI? I have this signature:
There is no secret syntax:
,--[ docs/pmc/struct.pod ]-
|Array Size
|The second initiali
> Speaking about parrotbug, are the [EMAIL PROTECTED] addresses
> created? What do they currently do?
parrotbug@ sends to the tracker
status-{ok,nok}@ currently end up in mailboxes that nobody reads
-R
> On 4/19/04 3:58 PM, Austin Hastings wrote:
> One work-around might be an alternate kind of default accessor that doesn't
> allow assignment:
>
> $dog.name # get
> $dog.name('foo') # set
> $dog.name = 'foo' # compile-time error
I think we already have this. Just define a
Chromatic <[EMAIL PROTECTED]> wrote:
> I played with making executables today (to no avail; it's having trouble
> with load_bytecode ops, but that's a different issue).
It's likely that this needs some runcore fiddling. Initially compiled
code resides in the executable, while additional code is a
Bernhard Schmalhofer (via RT) wrote:
In Parrot m4 0.0.4 there a couple of new builtin macros. The internal data
structure have been refactored in order to support some more features in the
future. However I haven't yet gotten around to start using objects.
Due to some new PIR syntax I could simpl
I've now checked in some changes WRT these opcodes.
1) Strings - summary
set Sx, Sy# alias Sx to Sy
set Sx, "str" # set Sx to COW copy of "str"
set Px, Sy# CHANGED make Px refer to Sy
assign Px, Sy # set Px to COW copy of Sy
2) PMC summary
set Px, Py# al
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> The interpreter stuff's simple enough--we teach the ops preprocessor
> to handle them the same way that it does string constants, and index
> into the PMC constant table. We'll want to put them in a separate
> part of the bytecode file,
Why I second table
On Mon, Apr 19, 2004 at 08:21:58PM -0400, Joe Gottman wrote:
:Apocalypse 12 was very clear about the difference between private and
: public class members, but it didn't say anything about protected ones? How
: can you define a protected member?
You can't. The concept of "protected" does not
What's the secret syntax for passing and retriving arrays of things to
and from NCI? I have this signature:
extern DECLSPEC void SDLCALL SDL_UpdateRects
(SDL_Surface *screen, int numrects, SDL_Rect *rects);
That'd be *very* handy to expose.
(Yeah, Dan, I know you said yo
Since this horse came back to life, I'm going to give it a good thrashing, and
I've got goons to help me.
I've asked the Phoenix Perl Mongers for their take on the situation. I've posted
a _completely_ unbiased synopsis of the situation. Here are excerpts from the replies:
Tony's take:
"Rename
71 matches
Mail list logo
