Re: PARROT_API, compiler and linker flags (was TODO: Linker magic step for configure)

2004-05-14 Thread Ron Blaschke
Friday, May 14, 2004, 11:48:00 PM, Andy Dougherty wrote: >> IMHO, we are currently talking C only, so that shouldn't be a problem. I >> hope anybody tells me if I'm wrong. >> Still, I am curious. Why would the linker need to know about C or C++? > I thought ICU contained some C++ files. As to

Re: PARROT_API, compiler and linker flags (was TODO: Linker magic step for configure)

2004-05-14 Thread Ron Blaschke
On Fri, 14 May 2004 09:11:32 +0200, Bernhard Schmalhofer wrote: > I have little expertise in building libraries on many platforms. But > aren't these issues all addressed by GNU's 'libtool'. Is there a > licensing reason for not using that? autoconf, automake and libtool address the issues we a

Re: PARROT_API, compiler and linker flags (was TODO: Linker magic step for configure)

2004-05-14 Thread Ron Blaschke
On Thu, 13 May 2004 17:23:18 -0700, Jeff Clites wrote: >> xxx_STATIC_BUILDcflags and ldflags to build static parrot > We should make it clear that we are talking about building a static lib > (to distinguish from what the next macro is intended for)--so how > about: > xxx_STATIC_LIB_BUILD or

Re: PARROT_API, compiler and linker flags (was TODO: Linker magic step for configure)

2004-05-14 Thread Ron Blaschke
On Thu, 13 May 2004 10:00:53 -0400 (EDT), Andrew Dougherty wrote: > You might want to review the patch I submitted about a year and a half ago > -- it's # 18319, and it included some (but certainly not all) of your good > ideas. Thanks, I'll do that. > I gather parrot's now trying to include stu

MMD changes in

2004-05-14 Thread Dan Sugalski
Some tests are failing, and there are still issues with parrotobject-derived thigns, but the changes are all in and should be a matter of getting the busted stuff un-busted. -- Dan --"it's like this"--- D

Re: MMD stuff

2004-05-14 Thread Dan Sugalski
At 10:48 AM -0700 5/14/04, Jeff Clites wrote: On May 14, 2004, at 9:04 AM, Dan Sugalski wrote: Today's project is to get all the MMD things actually using MMD. I've put in the first wave of changes (well, OK, second if you consider Leo's BXOR test as the first) and should get the rest of the st

Re: MMD stuff

2004-05-14 Thread Jeff Clites
On May 14, 2004, at 9:04 AM, Dan Sugalski wrote: Today's project is to get all the MMD things actually using MMD. I've put in the first wave of changes (well, OK, second if you consider Leo's BXOR test as the first) and should get the rest of the stuff in today. This part's a bit hackish but,

MMD stuff

2004-05-14 Thread Dan Sugalski
Today's project is to get all the MMD things actually using MMD. I've put in the first wave of changes (well, OK, second if you consider Leo's BXOR test as the first) and should get the rest of the stuff in today. This part's a bit hackish but, well, there you go. It does break some of the obj

CALL__BUILD

2004-05-14 Thread Jens Rieks
Hi, whats the plan WRT to CALL__BUILD? I've written a patch that makes it the default, but does a fallback to "__init" if no BUILD property is set. If the __init method does not exists, no exception is thrown (like before), whereas now an exception is thrown if you specify a BUILD property and

Re: Addition to compiler_faq.pod

2004-05-14 Thread Dan Sugalski
At 8:58 AM -0400 5/13/04, Sterling Hughes wrote: patch attached. gist: "how do i manage a simple case of lexical pads?" Applied. Now to get the darned things answered... -- Dan --"it's like this"--- Dan Sug

RE: Events (I think we need a new name)

2004-05-14 Thread Aaron Sherman
On Fri, 2004-05-14 at 06:27, Rachwal Waldemar-AWR001 wrote: > It seems the name 'event' is not as bad. So, maybe 'Pevent', stands for 'parrot > event'? > One advantage... it'd be easy searchable. I recall a pain whenever I searched for > 'thread', or 'Icon'. If you're talking about search engine

Re: Events (I think we need a new name) - Parcel?

2004-05-14 Thread Andy Wardley
Butler, Gerald wrote: > How about: "tocsin" [...thinking out loud...] I'm not sure it's a good idea to use an obscure word, even if it is appropriate to the usage. It should be a word that the average user would recognise, and hopefully be able to intuit some sense of what it does. How about "P

RE: Events (I think we need a new name) - Parcel?

2004-05-14 Thread Butler, Gerald
I LOVE IT: "PARrot Container for Event Lobbing!!!" -Original Message- From: Andy Wardley [mailto:[EMAIL PROTECTED] Sent: Friday, May 14, 2004 7:36 AM To: Butler, Gerald Cc: 'Gordon Henriksen'; '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: Re: Events (I think we need a new name) - Parce

RE: Events (I think we need a new name)

2004-05-14 Thread Rachwal Waldemar-AWR001
It seems the name 'event' is not as bad. So, maybe 'Pevent', stands for 'parrot event'? One advantage... it'd be easy searchable. I recall a pain whenever I searched for 'thread', or 'Icon'. Regards, Waldemar -Original Message- From: Dan Sugalski [mailto:[EMAIL PROTECTED] Sent: Wednesday

RE: Events (I think we need a new name)

2004-05-14 Thread Butler, Gerald
How about: "tocsin" toc.sin( P ) Pronunciation Key (tksn) n. An alarm sounded on a bell. A bell used to sound an alarm. A warning; an omen. -Original Message- From: Gordon Henriksen [mailto:[EMAIL PROTECTED] Sent: Thursday, May 13, 2004 2:52 PM To: [EMAIL PROTECTED] Cc: [EMAIL

Re: Events (I think we need a new name)

2004-05-14 Thread Clark C. Evans
On Wed, May 12, 2004 at 06:15:54PM +0200, K Stol wrote: | >It does, though, sound like we might want an alternate name for this | >stuff. While event is the right thing in some places it isn't in | >others (like the whole attribute/property mess) we may be well-served | >choosing another name. I

Re: Event design sketch

2004-05-14 Thread Rocco Caputo
On Tue, May 11, 2004 at 02:06:51PM -0400, Dan Sugalski wrote: > At 1:10 PM -0400 5/11/04, Uri Guttman wrote: > > >i don't think there is a need for all those variants. why would alarm > >need any special opcode when it is just a timer with a delay of abs_time > >- NOW? let the coder handle that an

Re: PARROT_API, compiler and linker flags (was TODO: Linker magic step for configure)

2004-05-14 Thread Andrew Dougherty
On Wed, 12 May 2004, Ron Blaschke wrote: > I have finally sorted out the details of the flags stuff, which I will > present below. Any comments are highly appreciated. Be warned: I am going > to implements this if there are no objections. ;-) You might want to review the patch I submitted about

Addition to compiler_faq.pod

2004-05-14 Thread Sterling Hughes
patch attached. gist: "how do i manage a simple case of lexical pads?" cfaq.diff Description: Binary data -sterling

Re: PARROT_API, compiler and linker flags (was TODO: Linker magic step for configure)

2004-05-14 Thread Bernhard Schmalhofer
Dan Sugalski wrote: At 5:23 PM -0700 5/13/04, Jeff Clites wrote: [Most commentary snipped, as it's dead-on] - When building / using a shared parrot the compiler macro PARROT_LIB_DYNAMIC will be defined, for static PARROT_LIB_STATIC What will these be used for? Traditionally, there aren't compile-