🚀 go-pugleaf

Can you elaborate on what "serious bugs" exist in the Microsoft class
libraries?  We have had only one minor bug report and posted a patch
on CompuServe (and I have reposted it here) having to do with changing the
background color of a dialog (pretty minor).  Other than that, we have had
no bug reports on CompuServe or USENET.  

Always glad to help, if you provide specifics,
Steven


In article <1992Aug8.210847.13563@cs.UAlberta.CA> ken@cs.UAlberta.CA (Huisman Kenneth M) writes:
>In article <1992Aug6.230926.12692@moe.einstein.com>, jasper@iris.einstein.com (John Scott Peter XXXIII) writes:
>> In article <1992Aug6.062043.28002@cs.UAlberta.CA>, ken@cs.UAlberta.CA (Huisman Kenneth M) writes:
>> > 
>> > We are currently trying to decide between
>> > borland c++ and microsoft c/c++ for windows development.
>> > 
>> > What are the relative strengths / weaknesses of these
>> > two products?
>> 
>> Please, post any opinions to the net.  I, and I'm sure a lot of other people,
>> would be interested in hearing opinions on the differences between BC and MSC.
>> Just about all I know about these 2 products is the features each has: the
>> biggest feature difference is that BC 3.1 has templates, and MSC 7.0 does not.
>> Otherwise, the list of development utilities seems comparable: both have
>> integrated environments.  BC's is Windows-based; MSC's can be run from Windows,
>> but seems to be character-video only.  Both have Windows development class
>> libraries, but I've heard that MSC's is not as "thick" a layer as BC's.  Both
>> have source/class browsers, and execution profilers, as well as the standard
>> debuggers, assemblers, etc.  Both have register parameter-passing, but only
>> MSC has a p-code generating option.
>> 
>> However, not having really used either product, I can't say how WELL each one
>> does what it does.  That's what I'd like other yoosers' opinions on.
>
>I got two replies via email to my origional question.  ( thanks to the two people
>who replied).  One was a Borland user, and was generally happy with 
>Borland's product.  The other was a Microsoft user who said he would not
>reccomment the microsoft compiler because of serious bugs in microsoft's
>class libraries.
>
>Ken
>
>(((((((((((((((((((((((((((((((((*))))))))))))))))))))))))))))))))))))
>(( Ken Huisman, Bsc.                                                ))
>(( Programmer, City of Edmonton                                     ))
>(( ---------------------------------------------------------------- ))
>(( email: ken@cs.ualberta.ca                                        ))
>(((((((((((((((((((((((((((((((((*))))))))))))))))))))))))))))))))))))
>


-- 
Steven Sinofsky
stevesi@microsoft.com
Disclaimer: I don't speak for Microsoft, BillG does that.