🚀 go-pugleaf

These dwrites were probably never run through any kind of QA
process or spec'd into the release.  Therefore they would not
have been documented.  Most users enjoy finding out about
"features" in the release.  It seems that you do not and therefor
should not use the feature.


In article <BwpFzF.58E@news.cso.uiuc.edu> jeffo@uiuc.edu (J.B. Nicholson-Owens) writes:
>So, on top of massive localization problems with their main documentation, we  
>now have this 'mystery' dwrite command absence of documentation.  This is  
>really sad that we can only get these dwrite commands whenever *NeXT* is  
>queried or (probably) if *NeXT* feels like giving them out.
>

Presenting your point of view in this manner does nothing
to help get things changed.  Future flames should be sent
to comp.sys.advocacy.

>They had this *same problem* with 2.1, if I remember the responses I received  
>from asking the same question when 2.1 was the latest OS.  Will they get it  
>together in 3.1?  Only NeXT can tell.
>-- 


-- 
Joe Freeman	jfreem@uncecs.edu
		jfreeman@next.com (NeXT Mail)
The opinions espressed here are my own and are not shared by my employer  or
anyone else I know of.  Flames can be mailed to me or routed to /dev/null.