Re: [WIP PATCH] core.ops split-up

"Brent Dax" <[EMAIL PROTECTED]> writes: > Anyway, a corrected patch that fixes the trans.t errors is up at > . Uh, there's still no "+inline op sin" in that file? > If it doesn't > apply the first time, try splitting the patch into several

RE: [WIP PATCH] core.ops split-up

Finally got some feedback through IRC--trans.t and object.t were failing. object.t works for me (miracle of miracles, considering the other test failures on Windows), but trans.t was easy to figure out--I'd copied the transcendental ops from core.ops and never pasted them into math.ops. *rolls ey

Unsubscribing (was RE: [WIP PATCH] core.ops split-up)

At 12:15 AM +0800 7/21/03, K.N.Vishwanath wrote: How do I get out of this list please? The mailing list software puts the list contact and unsubscribe information in every message that goes out--it's in the headers. In this case, the info is: List-Unsubscribe: --

RE: [WIP PATCH] core.ops split-up

How do I get out of this list please? Vish -Original Message- From: Dan Sugalski [mailto:[EMAIL PROTECTED] Sent: Monday, July 21, 2003 12:02 AM To: [EMAIL PROTECTED]; Benjamin Goldberg Cc: [EMAIL PROTECTED] Subject: Re: [WIP PATCH] core.ops split-up At 11:47 AM +0200 7/19/03, Leopold

Re: [WIP PATCH] core.ops split-up

At 11:47 AM +0200 7/19/03, Leopold Toetsch wrote: Benjamin Goldberg <[EMAIL PROTECTED]> wrote: Could we try and clean up the parrot/ directory? Specifically, I'd like all of the source code itself moved into a single subdirectory, leaving at the toplevel only directories, the all-caps files, a

Re: [WIP PATCH] core.ops split-up

Benjamin Goldberg <[EMAIL PROTECTED]> wrote: > Could we try and clean up the parrot/ directory? Specifically, I'd like > all of the source code itself moved into a single subdirectory, leaving > at the toplevel only directories, the all-caps files, and a few others > (ChangeLog, Configure.pl, par

Re: [WIP PATCH] core.ops split-up

Brent Dax <[EMAIL PROTECTED]> wrote: >core.ops is...monolithic. >core.ops could use a good splitting out, definitely That's ok for me. leo

Re: [WIP PATCH] core.ops split-up

Benjamin Goldberg <[EMAIL PROTECTED]> writes: > (ChangeLog, Configure.pl, parrot.spec, and whatever else is really > needed to build and distribute parrot (make.pl?)). Nothing is currently using make.pl, and it's way out of date compared to the configure system - delete it? -- Lars Balker Rasmuss

Re: [WIP PATCH] core.ops split-up

With this increase in the number of files, I'm going to ask for something I've thought of for a while, but not had the guts to ask for. Could we try and clean up the parrot/ directory? Specifically, I'd like all of the source code itself moved into a single subdirectory, leaving at the toplevel

RE: [WIP PATCH] core.ops split-up

Brent Dax: # Since I don't think it's polite to flood peoples' mailboxes, I have # uploaded the 205 kb (9213 line) patch to # . The version I originally posted contained a patch to classes/timer.pmc, basically disabling its guts. That was inc

[WIP PATCH] core.ops split-up

core.ops is...monolithic. core.ops could use a good splitting out, definitely At 108k, core.ops is the second largest file in the Parrot distribution. It's larger than all but five or six C files in bleadperl. It has nearly five hundred more lines than pp.c--and that's with seve