🚀 go-pugleaf

In article <316445a3.428887193@news.primenet.com>, gbe@primenet.com 
says...
>
>/* BugDemo.cpp
>
>   Here is a demonstration of a serious bug that I just found in 
Microsoft
>   Visual C++ Version 4.1. 

Debugging version of MS C/C++ compilerss of all versions have bugs - 
I find them each time when I forget to set options for using optimizing
version. Last time it happend yesterday on the following code fragment
(r defined as "long", bcode as "unsigned char []", compiler version is
1.52):

  // Next statement must be compiled with enabled optimizations
  // because of bug in MSVC 1.52 C++ compiler  
  if((r & 0xFF) != bcode[7] || ((r >> 8) & 0xFF) != bcode[6] ||
     ((r >> 16)  & 0xFF) != bcode[5])
    return -1; 

Address of bcode[7] was calculated incorrectly - actually it used
bcode[5] instead.

My practice to avoid that is to use only optimizing version of compiler
(even in case of all disabled optimizations).

-- 
<<< If you received it by E-mail: it is a copy of post to the newsgroup 
>>>
---------------------------------------------------------------
Michael Furman,                       (603)893-1109
Geophysical Survey Systems, Inc.  fax:(603)889-3984
13 Klein Drive - P.O. Box 97          engr@gssi.mv.com 
North Salem, NH 03073-0097            71543.1334@compuserve.com
---------------------------------------------------------------