On Sep-07, Leopold Toetsch wrote:
> Steve Fink <[EMAIL PROTECTED]> wrote:
>
> > This patch introduces something that feels suspiciously like libtool,
> > despite the fact that libtool has never been very kind to me. But for
> > now I am targeting this only at the dynamic PMC generation problem; th
Dan,
sorry, although I'm a long term perl user I'm not that familiar with the
internals of the perl development process that I know all the old
stories ;)
The plan looks good, but some things are still unclear to me:
> *) Person building runs platform-specific script
Platform specific means
When I try to run one of the SDL examples (any of them), I get:
SDL::fetch_layout warning: layout 'Pixels' not found!
Segmentation fault
When I edit runtime/parrot/library/SDL.imc and add the call to
_set_Pixels_layout in at line 60, I remove that warning, but still get
the seg-fault:
Program re
Juerd wrote:
Jonathan Lang skribis 2004-09-07 14:12 (-0700):
if we want to look at the next existing element, we can say (1 +
1).th; if we want to look at the element whose index is one higher
than the first index, we can say 1.st + 1.
I read this three times, but don't get it. Can you plea
On Tue, Sep 07, 2004 at 10:34:33PM -0400, John Macdonald wrote:
: If a int1 (or int2 or nybble or other sub-addressable sized
: value) is being referred to, a similar issue arises since most
: machines these days have byte addressing, but do not have bit
: addressing. If you can't refer directly t
Mark Overmeer <[EMAIL PROTECTED]> writes:
> Oops, someone starts the holy war (again). Wether you put the docs
> in begin or end of the file, or intermixed with the code has a lot
> to do with your personal background.
Sorry for the late reply, but I can't let this stand without further
elaborat
On Fri, Sep 03, 2004 at 11:20:05AM -0700, Larry Wall wrote:
> On Fri, Sep 03, 2004 at 11:41:05AM +0100, Tim Bunce wrote:
> : And that a pointer would be... what? Some platforms has odd
> : sizing issues for pointers. Perhaps a "voidp" type is needed?
> : (Which would just be an intN where N is size
On 9/7/04 6:31 PM, Gregory Keeney wrote:
> Dan Sugalski wrote:
>> Though it really ought to be on perl6-internals, since it's not really
>> a perl thing at all, rather a parrot thing. I don't think I've the
>> cycles to think about it for a while, though.
>
> Sounds like I need to dig through th
On Tue, 7 Sep 2004, Leopold Toetsch wrote:
> > [*] Unless it's a _feature_ that given tied $a,
> >($a = "aaa") =~ s/a/b/g
> > would call STORE four times ("aaa", "baa", "bba", "bbb").
>
> I'd expect two stores here. One for the initial setting of the value and
> one for the final result
On Tuesday 07 September 2004 03:47 pm, Nicholas Clark wrote:
> On Tue, Sep 07, 2004 at 10:52:01AM -0400, Aaron Sherman wrote:
> > Seriously, I've never come across any system that lacked autoconf
> > support AND which a high level language like those that would target
> > Parrot, ran on. If you're
Dan Sugalski wrote:
You've got things a bit turned around I think. Parrot's the engine. It
provides the services, runs the code, handles the environment, and
generally manages stuff. If you want, think of it as a combination
CPU, OS, low-level debugging tools, and standard system libraries that
At 3:31 PM -0700 9/7/04, Gregory Keeney wrote:
Dan Sugalski wrote:
Though it really ought to be on perl6-internals, since it's not
really a perl thing at all, rather a parrot thing. I don't think
I've the cycles to think about it for a while, though.
Sounds like I need to dig through the mail ar
Or, rather, the const_string function.
Simple thing, looks like:
STRING *foo = const_string(interpreter, c-style string constant);
Easy, right? Yeah. Easy. What it does is create a new parrot string,
set to the constant C string you pass in. Handy. Even marks the
string as constant and extern
Dan Sugalski wrote:
Though it really ought to be on perl6-internals, since it's not really
a perl thing at all, rather a parrot thing. I don't think I've the
cycles to think about it for a while, though.
Sounds like I need to dig through the mail archives, RFC's, etc. and try
to come up with a
This argument's old. Very old, so it may be unfamiliar to many
people. The subject generates enough heat that I don't want to go
there again.
We are not using autoconf. Period.
Parrot's build process, when shipped will be:
*) Person building runs platform-specific script
*) Script builds minipar
At 2:48 PM -0700 9/7/04, Gregory Keeney wrote:
Nicholas Clark wrote:
On Tue, Sep 07, 2004 at 06:07:24PM +0200, James Mastros wrote:
4. The single-file, platform dependent, machine language
executable (realexe). This is a plain old executable, that does
not particularly indicate it was generated
On Tue, 2004-09-07 at 11:59, Andrew Dougherty wrote:
> Both autoconf and metaconfig assume a unix-like environment. Ambitious
> plans for parrot's configure include non-unix environments too, such as
> VMS and all the ports where perl5 uses a manually-generated config.*
> template.
autoconf assu
Nicholas Clark wrote:
On Tue, Sep 07, 2004 at 06:07:24PM +0200, James Mastros wrote:
4. The single-file, platform dependent, machine language executable
(realexe). This is a plain old executable, that does not particularly
indicate it was generated by a "scripting" language. It requires no o
From perl6-language (Matt Diephouse essentially suggested that this
issue be brought here).
Smylers wrote:
John Siracusa writes:
To bring it home, I think packaging and distribution is important
enough to warrant a standard, core-supported implementation. Yes,
it's great to be able to roll yo
On Tue, Sep 07, 2004 at 06:07:24PM +0200, James Mastros wrote:
> 4. The single-file, platform dependent, machine language executable
> (realexe). This is a plain old executable, that does not particularly
> indicate it was generated by a "scripting" language. It requires no odd
> handing vs a
Jonathan Lang skribis 2004-09-07 14:12 (-0700):
> Again, with a bit of magic where the dot is optional when the object in
> question is an integer literal: 4th =:= 4.th - and probably with special
> synonyms for th when the literal is any of (1 or -1, 2 or -2, 3 or -3) -
> Number::st, Number::nd, a
On Fri, 2004-09-03 at 20:08, Larry Wall wrote:
> Arrays with explicit ranges don't use the
> minus notation to count from the end. We probably need to come up
> with some other notation for the beginning and end indexes. But it'd
> be nice if that were a little shorter than:
>
> @ints.shape
Juerd wrote:
> John Williams wrote:
> > > 4 :th
> > > $foo :th
> > No. Adverbs modify verbs (operators or functions), not terms like 4 or
> > $foo.
>
> Then perhaps a method? Number::th?
>
> 4.th
> $foo.th
Again, with a bit of magic where the dot is optional when the object in
qu
Hmm, this would suggest that in P6 the comment that "unlike ++,
the -- operator is not magical" should no longer apply.
On Fri, Sep 03, 2004 at 08:09:23AM -0400, Joe Gottman wrote:
>
>
> > -Original Message-
> > From: Larry Wall [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, September 02,
Hi,
the examples in examples/streams are not working with --gc-debug,
FileLines.imc crashes even without it.
Any idea why?
jens
Smylers wrote:
> (But personally I'm quite happy with zero-based arrays, so as long as
> -1 continues to work for those I'm not too bothered what happens with
> other cases.)
This is an interesting point: can the perl optimizer be made to treat
0-based contiguous lists in the same way that perl 5
Hi!
You can read various infos and look at some data in my use.perl journal:
http://use.perl.org/~domm/journal/20771
On issue I'd like to ask is: We (Gabor Szabo and I) are thinking of renaming
the distribution from "Module::CPANTS" to "CPANTS". Do you think that this
is a good idea?
IMO CPANT
Thomas Seiler skribis 2004-09-07 20:23 (+0200):
> I touhght that it be nice to let module writers somehow associate their
> module with a file extention.
Most worlds don't use file extensions, except for humans. In the Windows
world, file extensions do matter, because it decides which program to
On Tue, Sep 07, 2004 at 10:52:01AM -0400, Aaron Sherman wrote:
> Seriously, I've never come across any system that lacked autoconf
> support AND which a high level language like those that would target
> Parrot, ran on. If you're referring to the number of systems that have
autoconf supports Win3
James Mastros wrote:
We can, and I think should, write a one-paragraph documentation,
one-screenful implementation of this that's in perl core:
As a special case, if the "filename" argument to perl is a directory,
and the directory contains a file named "main.pl", then the directory
is prep
On Tue, 2004-09-07 at 09:26, Dan Sugalski wrote:
> *) Namespaces are hierarchical
>
> So we can have ["foo"; "bar"; "baz"] for a namespace. Woo hoo and all
> that. It'd map to the equivalent perl namespace of foo::bar::baz.
[...]
It's also possible to hoist a sub-space up a few levels, so that t
John Williams skribis 2004-09-07 12:49 (-0600):
> > 4 :th
> > $foo :th
> No. Adverbs modify verbs (operators or functions), not terms like 4 or
> $foo.
Then perhaps a method? Number::th?
4.th
$foo.th
I really dislike the apostrophe.
Juerd
On Tue, 7 Sep 2004, Juerd wrote:
> John Williams skribis 2004-09-07 11:37 (-0600):
> > > and postfix:'th? It's 80s and postfix:th!
> > Probably to help separate the term from the postfix operator.
> >@array[ $foo'th ];
>
> Maybe what I'm saying now is a really bad idea, because it doesn't make
On Tue, Sep 07, 2004 at 04:11:18PM +, Herbert Snorrason wrote:
> So ... it's actually happening? There's really going to *be* a Perl6?
> It's not just an april fool's gone wrong, like Parrot? ;)
Mark my words: There will be a Perl 6.
Pm
John Williams skribis 2004-09-07 11:37 (-0600):
> > and postfix:'th? It's 80s and postfix:th!
> Probably to help separate the term from the postfix operator.
>@array[ $foo'th ];
Maybe what I'm saying now is a really bad idea, because it doesn't make
sense, but can't we just have an adverb tha
i've made some good progress on mod_parrot. since so much has changed
in the past year, i decided to rewrite the thing from scratch. here's
what i've been able to implement so far:
* rewrite for apache 2 (might as well start with the latest)
* per-process interpreter persistence (using prefork M
On Tue, 7 Sep 2004, James Mastros wrote:
> PS -- Unreatedly, why, oh why, do people insist on an apostrophe in 80's
Maybe "in the 80's" is like "at the Jones's". Not that I care, mind you.
> and postfix:'th? It's 80s and postfix:th!
Probably to help separate the term from the postfix operator.
John Siracusa wrote:
1. The special dir of files (SDoF). Ignoring, for now, the argument for a
standard way to do this, all the core needs to do to bootstrap an entire
ecosystem of app packagers is support some standard starting point. Maybe
it's a file names main.pl inside a *.pmx dir, or whatev
On Tue, Sep 07, 2004 at 09:26:14AM -0400, Dan Sugalski wrote:
> Time to nail this.
>
> We need namespaces. Duh. We talked about this in the past.
I've reordered these to put the simple/fundamental things first:
> *) Namespaces are hierarchical
> *) The top-level namespace ["__INTERNAL"] is taken
For the case that someone does not know how to subscribe:
just send a mail to [EMAIL PROTECTED]
jens
So ... it's actually happening? There's really going to *be* a Perl6?
It's not just an april fool's gone wrong, like Parrot? ;)
On Tue, 7 Sep 2004 11:57:23 -0400, Dan Sugalski <[EMAIL PROTECTED]> wrote:
> The list... is open. It's meant for discussion of the perl 6 compiler
> specifically. Perl6-i
On Tue, Sep 07, 2004 at 10:52:01AM -0400, Aaron Sherman wrote:
> Ok, this is probably a moot conversation because Metaconfig
> (http://www.linux-mag.com/2002-12/compile_03.html) was written by Larry
> Wall for rn, and the Perl community has some serious social inertia when
> it comes to switching t
On Tue, 7 Sep 2004, Aaron Sherman wrote:
> On Tue, 2004-09-07 at 08:00, Jens Rieks wrote:
> > On Tuesday 07 September 2004 07:52, Robert Schwebel wrote:
> > > Would autoconf/automake be an option for the C part of parrot?
> > No, its only available on a few systems.
>
> Ok, this is probably a moot
The list... is open. It's meant for discussion of the perl 6 compiler
specifically. Perl6-internals (which will get renamed
parrot-internals... some day) is for parrot discussion. At some point
reasonably soon I'm told that parrot-compilers will be up and running
as well, for the discussion of
Andy Dougherty <[EMAIL PROTECTED]> wrote:
> "imcc/imcc.l", line 852:
> warning: improper pointer/integer combination: arg #2
Is already fixed.
> Still, it's probably a good step forward.
Ok.
leo
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 11:27 AM +0200 9/3/04, Leopold Toetsch wrote:
>>Dan Sugalski <[EMAIL PROTECTED]> wrote:
>>> At 12:16 PM +0200 8/31/04, Leopold Toetsch wrote:
Pclass = getclass, "Foo"
Pobjnew = Pclass."__new"(args) # Pnew is an OUT argument
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> *) Namespaces are hierarchical
What do we do against collisions? During Pie-thon hacking I came along
this problem:
class C():
pass
c = C()
"C" ought to be now a "global" classname (that's what the bytecode
indicates) and it should be its own na
On Tue, 7 Sep 2004 10:50:49 -0400 (EDT), Andy Dougherty
<[EMAIL PROTECTED]> wrote:
> Still, it's probably a good step forward. We might eventually decide we
> need pre- and post- triggers or other enhancements, but this is probably a
> good basis to start with.
Pre and post triggers would be pret
Hi,
Maybe someone will be interested in what I came up with to test sending
emails. Usually I use Mail::Mailer, but obviously I don't want to send
real emails during testing - at best, they won't go anywhere, and at
worst, they will go to real users and confuse them.
Now, I use in my code My::M
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 6:55 PM +0200 9/2/04, Leopold Toetsch wrote:
>>- do we keep these opcodes?
> Yes.
Ok.
>> If yes some permutations are missing.
> Yeah. I'd as soon leave them out until we need them.
Well, the asymmetry makes it harder for compilers to emit proper
On Tue, 2004-09-07 at 08:00, Jens Rieks wrote:
> On Tuesday 07 September 2004 07:52, Robert Schwebel wrote:
> > Would autoconf/automake be an option for the C part of parrot?
> No, its only available on a few systems.
Ok, this is probably a moot conversation because Metaconfig
(http://www.linux-ma
On Tue, 7 Sep 2004, Leopold Toetsch wrote:
> Andy Dougherty <[EMAIL PROTECTED]> wrote:
> > On Sun, 5 Sep 2004, Clayton O'Neill wrote:
>
> >> This adds support for setting triggers on specific config variables.
>
> > I'd be inclined to call that particular routine solaris_gccversion_cb,
>
> Should
At 8:03 AM -0600 9/7/04, Luke Palmer wrote:
Dan Sugalski writes:
Time to nail this.
We need namespaces. Duh. We talked about this in the past.
So, here's what I'm proposing. It'll be formalized into a PDD once we
hash things out.
*) Namespaces are hierarchical
So we can have ["foo"; "bar"; "b
At 11:27 AM +0200 9/3/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
At 12:16 PM +0200 8/31/04, Leopold Toetsch wrote:
Pclass = getclass, "Foo"
Pobjnew = Pclass."__new"(args) # Pnew is an OUT argument
and that be special-cased to call VTABLE_new according to calling
co
Dan Sugalski writes:
> Time to nail this.
>
> We need namespaces. Duh. We talked about this in the past.
>
> So, here's what I'm proposing. It'll be formalized into a PDD once we
> hash things out.
>
> *) Namespaces are hierarchical
>
> So we can have ["foo"; "bar"; "baz"] for a namespace. Woo
At 10:59 PM -0400 9/6/04, Chip Salzenberg wrote:
Just across the hall from m// is s/// ...
Considering the semantics of m// and especially s/// at the user
level, we'll probably[*] want to take snapshots of dynamic strings
(think P5's "FETCH" or overload '""'), and apply all the pattern
operations
Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> For Topaz, Scalar's interface included a function that would basically
> open the Scalar's hood, giving you a Buffer you could manipulate; then
> when you were done working with the Buffer, its modifications (if any)
> were propagated back down into the
At 9:17 AM -0400 9/7/04, Dan Sugalski wrote:
Time to nail this.
Dammit! Eudora's autocompletion feature bites me again. :( Should've
gone to l6i.
--
Dan
--it's like this---
Dan Sugalski even samurai
[EMAIL PROTECTED]
Time to nail this.
We need namespaces. Duh. We talked about this in the past.
So, here's what I'm proposing. It'll be formalized into a PDD once we
hash things out.
*) Namespaces are hierarchical
So we can have ["foo"; "bar"; "baz"] for a namespace. Woo hoo and all
that. It'd map to the equivale
Time to nail this.
We need namespaces. Duh. We talked about this in the past.
So, here's what I'm proposing. It'll be formalized into a PDD once we
hash things out.
*) Namespaces are hierarchical
So we can have ["foo"; "bar"; "baz"] for a namespace. Woo hoo and all
that. It'd map to the equivale
At 6:55 PM +0200 9/2/04, Leopold Toetsch wrote:
We still have a lot of unhooked ops w/o a definite opcode number.
These are mainly the non-branching compare opcodes currently located
in ops/experimental.ops.
These opcodes have some limited usefullness for e.g.
bool_val = (a < b) && (c > d)
i.e
On Tue, Sep 07, 2004 at 02:00:14PM +0200, Jens Rieks wrote:
> On Tuesday 07 September 2004 07:52, Robert Schwebel wrote:
> > Would autoconf/automake be an option for the C part of parrot?
> No, its only available on a few systems.
How do you mean that? You surely don't want to run the compiler dir
On Tuesday 07 September 2004 07:52, Robert Schwebel wrote:
> Would autoconf/automake be an option for the C part of parrot?
No, its only available on a few systems.
Some months ago, I tried to cross compile Parrot to ARM (Zaurus), and to
compile Parrot directly on the Zaurus, with no success (mos
[EMAIL PROTECTED] (Dan Hursh) writes:
> Um, on a somewhat unrelated note, having tried to get a department of
> mine to switch over to perl from csh and REXX of all things, I have
> co-workers I hope never see this.
They may need to write their own operating system if they want to avoid the
dodgy
> 31028 perl -i fails on Win32 unless a backup string is
> provided for -i option
Should that really be a bug? You can't delete open files on Win32 so what is
perl supposed to do?
Yves
Just across the hall from m// is s/// ...
Considering the semantics of m// and especially s/// at the user
level, we'll probably[*] want to take snapshots of dynamic strings
(think P5's "FETCH" or overload '""'), and apply all the pattern
operations to that snapshot. *However*, in the usual case
Simon Cozens wrote:
For heaven's sake. Have you even *seen* the Perl 5 internals? If you don't
trust things which are self-declared scary hackery to be stable, you probably
shouldn't be using Perl until Perl 6 comes out. And probably not until then.
Um, on a somewhat unrelated note, having tried to
[ We're down a handful this week... but not by much... thanks to Steve
Peters for going through some of the old ones and identifiying things
that can be closed. ]
Perl5 Bug Summary
http://rt.perl.org/rt3/NoAuth/perl5/Overview.html
Generated at Mon Sep 6 13:00:02 2004 GMT
Jens Rieks <[EMAIL PROTECTED]> wrote:
> Hi all,
> there are now two new examples:
Great.
> Minesweeper freezes after you have created some new fields (by clicking onto
> the smiley). I think it is a GC bug, because minesweeper does not even start
> with --gc-debug.
Repeatedly clicking the smile
Steve Fink <[EMAIL PROTECTED]> wrote:
> This patch introduces something that feels suspiciously like libtool,
> despite the fact that libtool has never been very kind to me. But for
> now I am targeting this only at the dynamic PMC generation problem; this
> solution could be expanded to ease port
Andy Dougherty <[EMAIL PROTECTED]> wrote:
> On Sun, 5 Sep 2004, Clayton O'Neill wrote:
>> This adds support for setting triggers on specific config variables.
> I'd be inclined to call that particular routine solaris_gccversion_cb,
Should the patch go in?
> Thanks.
> Andy Dougherty
71 matches
Mail list logo
