🚀 go-pugleaf

Would someone more knowing please refute this guys complaints.

In article <1992Apr11.021508.29048@ux1.cso.uiuc.edu>, mlanett@void.ncsa.uiuc.edu (Mark Lanett) writes:
> linton@marktwain.rad.sgi.com (Mark Linton) writes:
> 
> >I agree that interface builders are a good thing and the Next one
> >is quite nice.  I believe that dynamic loading is the important feature
> >missing from most C++ environments; I'm less convinced that
> >I need to be able to get "method not defined for this object" errors.
> 
> A friend bought a NeXT (he's an experiences MacApp/C++ developer) and has not
> been terribly impressed with NextStep. One of his biggest complaints is that
> he *isn't* getting "method not defined for this object". Next has their
> doesNotUnderstand message just swallow everything and not provide any error
> messages at all! The only way he's figured out to tell if a message is actually
> received and understood by the correct object is to step into every method
> dispatch. To top it off, which Obj-C allows typed objects, the Next IB cannot
> parse them; it requires everything to be 'id'. So even if he wants to type 
> things to reduce a really ridiculous number of runtime errors... he can't.
> Maybe 3.0 will be better.
> -- 
> Mark Lanett, Software Tools Group, NCSA           mlanett@uiuc.edu or  NCSA.STG
-- 
shirley@bush.jsc.nasa.gov
[