[prev] [thread] [next] [lurker] [Date index for 2005/04/24]
On Sat, Apr 23, 2005 at 05:22:10PM -0500, Peter da Silva wrote: > > > 3. The implementation language is tightly bound into the API. Components > > > communicate through APIs that are written in terms of C++ classes and > > > objects. > > No worse than all the bits of Unix API that are defined in terms of C > > structs. > > mktime > mktime(3) is not a system call. It's part of "the Unix API". But if you insist on something that is more intimately tied to Unix, try stat, which is even more hateful. > > Or look at gettimeofday, one argument to which is a struct containing > > two longs. Now I have to guess whether long == int, or whether long is > > twice as big as an int - because the size of 'long' isn't defined anywhere! > Yes, I remember hating the fact that they decided to wimp out and NOT make > long 64 bits on the VAX in 1980. But you only have to learn that once for > an implementation You misunderstand my Hate. I hate that long is *not defined*, just like I hate that a struct is *not defined*. If it were defined I really wouldn't care whether it was 32 bits or 64 bits, because I could just write code to build the structure using my language of choice. -- David Cantrell | London Perl Mongers Deputy Chief Heretic "The whole aim of practical politics is to keep the populace alarmed (and hence clamorous to be led to safety) by menacing it with an endless series of hobgoblins, all of them imaginary" -- H. L. MenckenThere's stuff above here
Generated at 01:00 on 03 May 2005 by mariachi 0.52