Bug hunt

Anonymous — Thu, 13 Mar 2003 11:53:48 GMT

AcDb::kForRead'in when I should have been
AcDb::kForWrite'n. 5 hours to track down
that bug, and it only raised its head with
abortTransaction().

That was not fun.
Paul Kohut

Re: Bug hunt

Anonymous — Fri, 14 Mar 2003 09:44:28 GMT

I can't understand the need for this complication read - write business. Is
it heaps fatser to read then to write so it deserved such a complicated
approach?
Besides Autodesk gurus should be able to know when we're reading and when
we're not, or at least be more strict for example
const AcDbEntity *openForReading();
and
AcDbEntity* openForWriting();
this way the user can't change the const data if he's reading it and would
minimize the occurances of many bugs.

"Paul Kohut" wrote in message
news:1896698681902955E151E1B6C735B9D2@in.WebX.maYIadrTaRb...
> AcDb::kForRead'in when I should have been
> AcDb::kForWrite'n. 5 hours to track down
> that bug, and it only raised its head with
> abortTransaction().
>
> That was not fun.
> Paul Kohut
>
>

topic Re: Bug hunt in ObjectARX Forum

Bug hunt

Re: Bug hunt