On Sep-20, Dan Sugalski wrote:
>
> Now, the issue is how to actually build a compiler. Right now a
> compiler is a simple thing -- it's a method hanging off the __invoke
> vtable slot of the PMC. I'm not sure I like that, as it seems really,
> really hackish. Hacks are inevitable, of course, bu
On Sep-22, Will Coleda wrote:
> ld: /Users/coke/research/parrot/blib/lib/libparrot.dylib is input for the dynamic
> link editor, is not relocatable by the static link editor again
> compile foo.c failed (256)
>
> As for the next error... huh?
Not surprising. What architecture and linker are you
Attached, find a patch that does a first pass of this.
I skipped the SDL IMC's because one of them gave me trouble, but didn't include them in the root.in
I skipped the PASM files, as they appear to have PIR counterparts.
There are two files that are commented out, as they also gave me trouble.
I
At 7:32 PM -0700 9/22/04, Jeff Clites wrote:
On Sep 22, 2004, at 10:58 AM, Dan Sugalski wrote:
*) There are three things that can be in a namespace: Another
namespace, a method or sub, and a variable.
*) The names of namespaces, methods & subs, and variables do *not*
collide. You may have a name
On Sep 22, 2004, at 5:30 PM, Will Coleda (via RT) wrote:
# New Ticket Created by Will Coleda
# Please include the string: [perl #31682]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31682 >
...
$ make realclean
$ export LD_
On Sep 22, 2004, at 10:58 AM, Dan Sugalski wrote:
*) There are three things that can be in a namespace: Another
namespace, a method or sub, and a variable.
*) The names of namespaces, methods & subs, and variables do *not*
collide. You may have a namespace Foo, a sub Foo, and a variable Foo
at
First off, I'll point out that this belongs on p6l and nowhere else.
Edward Peschko writes:
> It all comes down to what you think is a 'low level' op.. Some
> languages think that regular expressions themselves aren't low level
> enough to be included in the language, perl thinks that it is
> low-
# New Ticket Created by Will Coleda
# Please include the string: [perl #31682]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31682 >
Trying to get dynclasses/Tcl* working with the new "group" directive.
Following the d
On Wed, Sep 22, 2004 at 01:58:17PM -0400, Dan Sugalski wrote:
> Okay, this is going to be a three parter. The second part is entirely
> structural, and mostly a matter of convention. (It's second because
> the sensible thing to do is go over the link Tim posted to the
> previous discussion and m
Just committed a change to Tcl that improves startup time noticably. (so, the test
suite runs muuuch faster)
I had switched to using "load_bytecode" of .imc files instead of .include - since I
was loading the .imc, the code had to be recompiled each time. Now, everything under /tcl/ is
compiled
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #31674]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31674 >
The INSTALL file in languages/m4/INSTALL says:
'libpcre' is required.
but, un
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #31673]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31673 >
languages/m4/src/eval.c includes a header . My Solaris 8 system
doesn't have such
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #31672]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31672 >
Solaris make had trouble with the $< variable in languages/m4/Makefile.
This patch
# New Ticket Created by Dan Sugalski
# Please include the string: [perl #31681]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31681 >
Most of the support's in, we just need to finish it. We just need to
get the tailcal
The Perl 6 Summary for the week ending 2004-09-17
Another week, another summary, and I'm running late. So:
This week in perl6-compiler
The current state of the compiler
Discussion of the current state of the nascent perl 6 compiler and how
best to contribute to its development even b
# New Ticket Created by Dan Sugalski
# Please include the string: [perl #31680]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31680 >
All the .imc and .pasm files in the library which aren't meant to be
.included shoul
At 12:33 PM -0700 9/22/04, chromatic wrote:
On Wed, 2004-09-22 at 12:21, Dan Sugalski wrote:
Larry's told me that as far as he's concerned the sigil is now part
of the variable name. So perl doesn't *have* a variable foo -- it has
$foo, @foo, %foo, and so on. (Granted, methods/subs are &foo, but
On Wed, 2004-09-22 at 12:21, Dan Sugalski wrote:
> Larry's told me that as far as he's concerned the sigil is now part
> of the variable name. So perl doesn't *have* a variable foo -- it has
> $foo, @foo, %foo, and so on. (Granted, methods/subs are &foo, but for
> that I'm OK slipping some choc
At 11:23 AM -0700 9/22/04, Will Coleda wrote:
On Wed, Sep 22, 2004 at 01:58:17PM -0400, Dan Sugalski wrote:
Okay, this is going to be a three parter. The second part is entirely
structural, and mostly a matter of convention. (It's second because
the sensible thing to do is go over the link Tim p
At 12:01 PM -0700 9/22/04, Brent 'Dax' Royal-Gordon wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
*) The names of namespaces, methods & subs, and variables do *not*
collide. You may have a namespace Foo, a sub Foo, and a variable Foo
at the same level of a namespace.
Why? Perl can use sigil ma
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> *) The names of namespaces, methods & subs, and variables do *not*
> collide. You may have a namespace Foo, a sub Foo, and a variable Foo
> at the same level of a namespace.
Why? Perl can use sigil mangling here, as it does with variables;
where else is t
On Wed, 2004-09-22 at 10:49, Luke Palmer wrote:
> Let me come right round to my point about perl being open source.
> Someone has to do the work somewhere, and making it "standard" or "core"
> doesn't change that. It just means that it'll take longer.
It also means that there's a possibility tha
Okay, this is going to be a three parter. The second part is entirely
structural, and mostly a matter of convention. (It's second because
the sensible thing to do is go over the link Tim posted to the
previous discussion and more or less Make It So. I'm having a hard
time getting a solid chunk
Edward Peschko writes:
> > > If you need to match the regex engine in reverse, in a totally unattached way
> > > via subroutine, then I would think the chance for subtle mistakes and errors
> > > would be exceedingly great.
> >
> > I don't understand how.
>
> it means that you have to reimpleme
Edward Peschko wrote:
yes, i see this is cool. I'd just hope that there would be an equivalent set of
rules that matches the entire regular expression engine, and distributed with
the 'standard' perl6 distribution if there is such a thing.. And that there isn't
too much of a performance hit in the
Just committed a change to Tcl so that all args attempt to retain their original PMC
values where possible (until now, all arguments were PerlStrings, all return values
were simple strings), and commands can now return something other than a string as a
result. This is a pre-requisite for using
Hi,
On Tue, 21 Sep 2004, Kevin Scaldeferri wrote:
> This patch gets rid of that error, and now my server starts up. I
> admit that I don't really understand its magic (eval 'BEGIN{1}'???),
> but it's progress.
What you call magic actually forces perl to run function 'runops_cover'
(see Cover
> > The reason for the modifier (or even a new operator (g/" for example) is that
> > you can easily test your regular expressions. The interface is trivial - all you
> > have
> > to do is switch your m/ out for g/, and sit back and see how your patterns
> > translate
> > into strings.
>
> Ye
> > ok, cool, I'm beginning to understand perl6 patterns a bit better.
> > Just a tiny request though (and I seem to remember this being
> > discussed)
>
> You were the one who initiated the thread :-)
>
Ah yes, I forgot about that. Damn brain cells.. ;-)
> > - I wish that there was an easy syn
Will Coleda <[EMAIL PROTECTED]> wrote:
> This shows the same mis-reporting of the error:
Fixed. Thanks for reporting.
leo
Will Coleda <[EMAIL PROTECTED]> wrote:
> It would be nice if we had some syntactic sugar in PIR, such that:
> .sub main @MAIN
> .local int foo = 1
> print foo
> end
> .end
Well, if it's a constant, you can already write:
.const int foo = 1
> ... for any type of intializer code...
> .l
31 matches
Mail list logo
