Andy Dougherty:
# On Thu, 21 Nov 2002, Leon Brocard wrote:
#
# > ps You might be concerned about the name. Well, CPAN has a module
# >which matches /fuck/ too. However, if everyone really thinks
# >it is a problem, I don't see a problem with s/fuck/funk/g
#
# Well, I'll speak up. I fin
How about s/fuck/fork/?
--Josh
(mmm.. brainspork)
At 22:59 on 12/03/2002 EST, Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 8:23 PM -0500 12/3/02, Andy Dougherty wrote:
> >On Thu, 21 Nov 2002, Leon Brocard wrote:
> >
> >> ps You might be concerned about the name. Well, CPAN has a module
> >>
At 8:23 PM -0500 12/3/02, Andy Dougherty wrote:
On Thu, 21 Nov 2002, Leon Brocard wrote:
ps You might be concerned about the name. Well, CPAN has a module
which matches /fuck/ too. However, if everyone really thinks
it is a problem, I don't see a problem with s/fuck/funk/g
Well, I'll
On Sep-18, John Williams wrote:
> # New Ticket Created by John Williams
> # Please include the string: [perl #17397]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=17397 >
>
>
> The attached patch makes assignment hyper
# New Ticket Created by Steve Fink
# Please include the string: [perl #18856]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18856 >
Here's a patch with a few minor fixes and one new feature. It requires
some discussion (or
On Dec-03, Dan Sugalski wrote:
> (Anyone feel like making some OpenGL ops? :)
Coincidentally, I have been seriously considering exactly that
recently. It happens to be right at the convergence of my day job and
hobby, and would serve as a useful demonstration of a couple of things
to both sides of
On Tue, 3 Dec 2002, Andy Dougherty wrote:
> On Thu, 21 Nov 2002, Leon Brocard wrote:
>
> > ps You might be concerned about the name. Well, CPAN has a module
> >which matches /fuck/ too. However, if everyone really thinks
> >it is a problem, I don't see a problem with s/fuck/funk/g
>
> Well
On Thu, 21 Nov 2002, Leon Brocard wrote:
> ps You might be concerned about the name. Well, CPAN has a module
>which matches /fuck/ too. However, if everyone really thinks
>it is a problem, I don't see a problem with s/fuck/funk/g
Well, I'll speak up. I find the name needlessly crude an
On Tue, 3 Dec 2002, Dan Sugalski wrote:
> At 4:29 PM -0500 12/3/02, David Robins wrote:
> >Enlightenment appreciated as always.
>
> This is something that'll come up with perl 6 reasonably soon as
> well. The solution for us is to have truth and falsehood be an
> optional property on the variable,
On Tue, Dec 03, 2002 at 05:09:43PM -0500, Dan Sugalski wrote:
> At 5:03 PM -0500 12/3/02, Michael Collins wrote:
> >The principal coders, do they work on this project full-time?
>
> Not for pay, no. I'm not sure anyone works on it full-time, though I
> may come closest.
The perl foundation was a
At 5:03 PM -0500 12/3/02, Michael Collins wrote:
The principal coders, do they work on this project full-time?
Not for pay, no. I'm not sure anyone works on it full-time, though I
may come closest.
And is there any source of funding for this project?
Nope.
Is there any formal structure to
I appologize for this, it's my second neophyte question in as many months, but
I'm curious about the structure of the Parrot development organization.
The principal coders, do they work on this project full-time?
And is there any source of funding for this project?
Is there any formal structure
At 4:29 PM -0500 12/3/02, David Robins wrote:
Enlightenment appreciated as always.
This is something that'll come up with perl 6 reasonably soon as
well. The solution for us is to have truth and falsehood be an
optional property on the variable, potentially separate from the
variable's value.
At 4:36 PM -0500 12/3/02, Dan Sugalski wrote:
At 12:05 PM -0800 12/3/02, Jonathan Sillito wrote:
(Would someone like to put the attached file into examples/assembly and
commit it? Also could someone look at the patch in #18419?)
Attached files are in, and I'll go dig up that patch and apply it.
Dan Sugalski sent the following bits through the ether:
> pthreads tends to want to be part of the initial program load.
FYI adding -lpthreads to C_LIBS and rebuilding parrot makes it work
for me. Now to get the hand of the signatures...
Leon
--
Leon Brocard.http://w
At 12:05 PM -0800 12/3/02, Jonathan Sillito wrote:
The example file has gotten out of date, thanks for pointing this out. The
attached example file fixes this. Also the lexical ops are documented in
core.ops and in the file docs/core_ops.pod which is generated from the
core.ops file at compile tim
On Thu, Nov 21, 2002 at 12:54:17PM +, Leon Brocard wrote:
> # New Ticket Created by Leon Brocard
> # Please include the string: [perl #18566]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=18566 >
>
>
> I've posted
Yes, me again
Most of the time, in the PMC logical_not method, one can write:
void logical_not (PMC* dest) {
dest->vtable->set_integer_native(INTERP,dest,NOT_SELF);
}
where NOT_SELF is 0 if we're "true" and 1 if we're "false". Or just leave
it out and let default blow up if
The Perl 6 Summary for the week ending 20021201
Oh look, it's only Monday evening and Piers has started writing this
week's summary. What is the world coming to?
As usual, we start with the internals list.
C#/Parrot Status
During last week's discussion of C# and Parrot, Nicholas
The example file has gotten out of date, thanks for pointing this out. The
attached example file fixes this. Also the lexical ops are documented in
core.ops and in the file docs/core_ops.pod which is generated from the
core.ops file at compile time. Also the tests in t/op/lexicals.t all work.
The
If memory serves me right, Leopold Toetsch wrote:
> Therefore these changes were necessary:
Is there any other way to feed imcc code other than via writing to a
file and running it ?...
My work needs a lot of string substitutions to work with the new IMCC ...
Dan was saying something like a C int
Okay, I've finally stopped waffling. The current PMC structure is now
officially frozen, modulo the odd twiddling to it. As such, I've
added a pmc.ops file and I'm starting to add in ops to read and write
bits of PMCs internals. Stuff for buffers/strings will be along at
some point reasonably s
The hash_destroy function is in include/parrot/hash.h but not defined (or
invoked) anywhere. I presume this is because hashes are GC'd, so
hash_destroy can now be removed from the header file?
I take it the design of lexicals is still undecided, as
examples/assembly/lexicals.pasm coughs up errors
At 2:05 PM -0800 11/30/02, Bryan Hundven wrote:
The idea is your choosen architecture (alpha, sparc, ix86, ppc, etc...)
boots up and instead of loading an "Operating System", it loads a
platform dependant layer, that in-turn has its own "CPU" and "Memory",
etc... that you write your operating syst
On Tue, Dec 03, 2002 at 04:53:45PM +0100, Leopold Toetsch wrote:
> Art Haas wrote:
> >
> >Sorry, it doesn't. I still get the same error message.
>
> If was rubbish. I did check in a now hopefully working fix.
> leo
A cvs update and 'make' confirms your changes allow imcc to build.
Thanks.
--
T
At 4:49 PM + 11/30/02, Alin Iacob (via RT) wrote:
As I read the PDDs I notice that some of them say 'perl' where it
should really say 'parrot' (remnants from the pre Parrot era?)
This patch clears some of the confusion.
Applied, thanks.
--
Dan
--
Art Haas wrote:
Sorry, it doesn't. I still get the same error message.
If was rubbish. I did check in a now hopefully working fix.
leo
On Tue, Dec 03, 2002 at 11:59:15AM +0100, Leopold Toetsch wrote:
> Art Haas wrote:
>
> >Hi.
> >
> >I've been building parrot for a while, and this problem has just started
> >in the last day or two. The 'imcc.y' file doesn't agree with bison ...
> >
> >$ cd languages/imcc
> >$ make
> >bison -v -y
Name clashes between parrots PASM language and imccs PIR syntax did
prohibit the mix of both flavors. Additionally imcc used "ret" to end
subroutine parsing, which didn't allow multiple return statements in
one sub.
Therefore these changes were necessary:
Tossed:
- push var ... use .arg or .retu
Art Haas wrote:
Hi.
I've been building parrot for a while, and this problem has just started
in the last day or two. The 'imcc.y' file doesn't agree with bison ...
$ cd languages/imcc
$ make
bison -v -y -d -o imcparser.c imcc.y
imcc.y:530.10-531.19: type clash on default action: != <>
Does t
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #18832]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18832 >
Attached patch tries to append building libnci$(SO) to the test_prep
target. I don't
Hi.
I've been building parrot for a while, and this problem has just started
in the last day or two. The 'imcc.y' file doesn't agree with bison ...
$ cd languages/imcc
$ make
bison -v -y -d -o imcparser.c imcc.y
imcc.y:530.10-531.19: type clash on default action: != <>
make: *** [imcparser.c] Er
David Robins wrote:
These all using the 2002-12-02_16 snapshot.
1. Can't ret early from .subs - looks like the parser sees a ret and figures
that's the end of the sub.
Yes. Imcc parses and produces code per subroutine, which are delimited
by ".sub" and "ret". A proposal was, to change
33 matches
Mail list logo
