OODL: Perl is.

1999-07-22 Thread DeRobertis
Hmmm... whoever was interested in using perl to write the intepreter, check out: http://www.perl.com/cgi-bin/pace/pub/1999/06/perl5-6.html

Re: OODL: XBlockFile - statistics

1999-07-22 Thread DeRobertis
At 1:36 PM +0200 on 7/21/99, M. Uli Kusterer wrote: But could you please post the tester so I can run it under Linux? And maybe expand it into a full regression test? The only thing for testing I have is in HelloWorld.cpp. I must of somehow not compiled that in. BTW -- what's the ANSI

Re: OODL: Any array classes

1999-07-22 Thread DeRobertis
At 11:58 PM -0400 on 7/21/99, [EMAIL PROTECTED] wrote: is it ok if I use iterator instead of iterator_const? The only difference is that const_iterator won't let you write directly to an element. So, you should be fine using a plain ol' iterator. Trouble is, in the long term I'd like to add

Re: OODL: Re: Report on XBlockFile's Linux Compilation

1999-07-22 Thread DeRobertis
At 5:59 PM +0200 on 7/21/99, M. Uli Kusterer wrote: Multi-character constants are not allowed. Why are there any in XBlockFile? We should do this in a compatable manner. An enum would be better -- one that uses integers, not character constants. Anthony, it eases debugging if field types are

Re: OODL: OODL - OC Licence - Copyright Holder

1999-07-22 Thread DeRobertis
At 1:24 PM +0200 on 7/21/99, M. Uli Kusterer wrote: Alain: YES and no. There could be some bickering. A difference of opinion concerning the importance of the contribution made by someone that wishes to be cited as one of the authors. Alain, in that event we would have the list decide on what

Re: OODL: Re: forking opencard

1999-07-22 Thread M. Uli Kusterer
At 9:25 AM -0400 on 7/21/99, [EMAIL PROTECTED] wrote: Your rule should be, anyone can fork the source and call it something different, but it has to end with -Card. Like OtherCard, AlterCard, Differencard, etc. Someone wants better color support and they write ColorCard; someone else really likes

Re: OODL: Any array classes

1999-07-22 Thread M. Uli Kusterer
I bet I can write a faster block file system :) Anthony, why don't you tell me what slow techniques I'm using and how to replace them with faster ones? This would maybe now take more time, but as I'd learn techniques to speed up my programs, my future code for OpenCard would be as fast as

Re: OODL: Goofball OT question

1999-07-22 Thread M. Uli Kusterer
I thought a lot about this, and I don't see why one couldn't "optionally" specify the type of a variable. Once the type was declared it would be unable to be used in any other context (until we added implicit or explicit conversion), but the advantage could be a performance increase for

OODL: Licenses - Fourth World Public License

1999-07-22 Thread M. Uli Kusterer
Hi folks, just thought for completeness' sake I'll throw this in also. It sounds pretty close to what we want, although I'm not sure we want to restrict distribution of an OpenCard clone that sets out to replace OpenCard. I think we should allow that, too. But maybe we could use it, as

Re: OODL: Re: Report on XBlockFile's Linux Compilation

1999-07-22 Thread M. Uli Kusterer
But, for the record, use 0x4d415020ul for 'MAP '. I've created the following macro for types: #define BLOCK_TYPE( a,b,c,d ) ((unsigned long)(d | (c 8) | (b 16) | (a 24))) Which should solve the problem. I use this whenever defining a constant for block type. Ok. You made me thing

Re: OODL: Any array classes

1999-07-22 Thread M. Uli Kusterer
Don't use GetInd calls. Use iterators. Why do the biggest problems always have the simplest solutions? Of course! Cheers, -- M. Uli Kusterer http://www.weblayout.com/witness 'The Witnesses of TeachText are