Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!usc!ucsd!ogccse!blake!dlarson
From: dlarson@blake.acs.washington.edu (Dale Larson)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Commodore Development Guidelines
Message-ID: <4445@blake.acs.washington.edu>
Date: 14 Nov 89 20:12:16 GMT
References: <4186@blake.acs.washington.edu> <488@glyph.UUCP> <4203@blake.acs.washington.edu> <8423@cbmvax.UUCP> <17328@kuhub.cc.ukans.edu>
Reply-To: dlarson@blake.acs.washington.edu (Dale Larson)
Organization: The Evergreen State College,  WA
Lines: 27

In article <17328@kuhub.cc.ukans.edu> 2FHDDOWEL@kuhub.cc.ukans.edu (John A. Thywissen) writes:
>In article <8423@cbmvax.UUCP>, mks@cbmvax.UUCP (Michael Sinz - CATS) writes:
>> We are trying to discurage the use of CreateStdIO().  Since both of these
>> are linker libraries, this is no real problem.  Also, CreateStdIO() will
>> now just do a CreateExtIO() with sizeof(struct IOStdReq)
>
>Where can one find out about these development policy decisions
>Commodore makes?  I am a Certified Developer, have the White and Blue
>RKMs, AutoDocs 1.2 & 1.3, etc. and STILL didn't know about this.

I was a Certified Developer for one or two years.  All I ever had to show
for it was Amiga Mail, A1000 schematics and invites to conferences way
out of my budget and geography.  That is why I quit paying Certified
Developer dues and that is why I am always asking dumn questions to the
net.

I had very seriously considered signing up as a developer again because I
had heard a lot about the guidelines and new docs and etc (and because I 
thought I could get work to pay for it :-)  but it looks like things haven't
changed much.  I guess if you are a company and pay the $600 year dues you
get to see the guidelines and etc.


-- 
	    A lack of prior planning on the part of any programmer 
		       always constitutes an emergency.
	
           Digital Teddy Bear      dlarson@blake.acs.washington.edu