btrieve bug
Robert Story
story at can503.UUCP
Fri Nov 10 05:52:23 AEST 1989
We (embarrassingly) use btrieve as our file manager on Xenix. For anyone else
using it you should be aware of a bug which was introduced in the latest
release of 4.11. The interface code contains a line which assigns the pid to
the global returnPID. This is as it was in earlier releases except that now
it is done within the initialization code. I assume this was done so that the
assignment would not be done each time that btrieve() was called. Fair
enough, except that if your process forks you will never read any messages off
the queue as you will be looking for those messages of your ppid!! Ergo, I
also assume that the person who made this change is a DOS programmer. (I
believe that btrieve was originally a DOS product. Oh would that it would
have stayed thus).
These opinions are not shared by my employer, for indeed, he has none.
--
[ Robert Story ..{!utzoo!censor, uunet!attcan!lsuc}!avcocan!story ]
[ SnailMail : AFS 201 Queens Avenue London Ontario Canada N6A 1J1 ]
[ or : AFS 3349 Michelson Drive Irvine California USA 92715-1606 ]
[ Voice : +1 519 672-4220 xtn 233 ]
More information about the Comp.unix.xenix
mailing list