Re: Thoughts on vtables...

On Sun, Dec 02, 2001 at 02:21:38AM -0500, Jeff G wrote: > Currently vtable.h is dynamically constructed from what would appear > to be a union of all possible operators on {int,num,string}. Now, this > is certainly handy (especially after having to cast one type to another, > and making heavy us

Cranky compilers

As has been pointed out to me, GCC is excessively permissive by default. So... We need a probe in configure.pl for GCC as the C compiler, and we need to have -Wall as a default switch on GCC builds. All builds should go without complaint to be considered passing. Jarkko's got some truly fascist

Re: Thoughts on vtables...

Simon Cozens wrote: > > On Sun, Dec 02, 2001 at 02:21:38AM -0500, Jeff G wrote: > > Currently vtable.h is dynamically constructed from what would appear > > to be a union of all possible operators on {int,num,string}. Now, this > > is certainly handy (especially after having to cast one type to

RE: Thoughts on vtables...

Jeff G: # Simon Cozens wrote: # > On Sun, Dec 02, 2001 at 02:21:38AM -0500, Jeff G wrote: # > > Currently vtable.h is dynamically constructed from what # would appear # > > to be a union of all possible operators on # {int,num,string}. Now, this # > > is certainly handy (especially after having

Ask not what tests can do for you...

I've modified all the trans math tests and PMC tests to check floating point operations by using a nearly-equal-to comparison macro rather than using perl to generate sprintf("%f"...) expected output. If you're writing any new tests which check floaty things, can you follow the style of these tes

Re: Thoughts on vtables...

On Sun, Dec 02, 2001 at 02:15:08PM -0500, Jeff G wrote: > Are you quite sure? Implementing things like arrays of PMCs will be hard > without operations like set_value(PMC* pmc, INTVAL index). This is why I'm waiting for Dan to come up with the explanation of how kesy are going to work. > > I d

RE: Cranky compilers

Dan Sugalski: # As has been pointed out to me, GCC is excessively permissive by # default. So... # # We need a probe in configure.pl for GCC as the C compiler, # and we need to # have -Wall as a default switch on GCC builds. All builds # should go without # complaint to be considered passing. It

Re: Thoughts on vtables...

On Sunday 02 December 2001 02:47 pm, Brent Dax wrote: > Quick comment: I've been thinking about constructing an 'OpaqueHandle' > PMC type.  All the programmer is supposed to know about it is that it > points to Something (usually a C struct, but they don't have to know > that).  I'm not sure what

Re: Thoughts on vtables...

On Sun, 2 Dec 2001, Michael L Maraist wrote: > On Sunday 02 December 2001 02:47 pm, Brent Dax wrote: > > Quick comment: I've been thinking about constructing an 'OpaqueHandle' > > PMC type.  All the programmer is supposed to know about it is that it > > points to Something (usually a C struct, bu

OT, but a good read anyway.

http://kerneltrap.org/article.php?sid=398 Parallels are obvious. Courtesy of /. -- Bryan C. Warnock [EMAIL PROTECTED]

[PATCH] Very small, very crude implementation of PerlArray

Because of the problems I've had sending diffs to the list, I'm just putting this onto my webserver at . This is a *VERY* crude implementation of a very limited array in Parrot. In addition to the PerlArray class, it also adds two new instructions to th