🚀 go-pugleaf

In article <5625@cbmvax.UUCP> jesup@cbmvax.UUCP (Randell Jesup) writes:
>In article <3638@tekig5.PEN.TEK.COM> brianr@tekig5.PEN.TEK.COM (Brian Rhodefer) writes:
>> messages I pass it, I've decided to try to use an IOExtSerReq
>> (OrWhatEverTheBleepItzCalled) whose ReplyPort field is NULL.
>
>	NULL??!!!  ALL IO requests must have the address of a valid port
>in the ReplyPort field.  No exceptions.
>

[ lots of stuff deleted ]

>	NULL is right out.  ReplyMsg on a message with a null replyport will
>corrupt low memory, leading to a quick crash.

This is very odd.  I am looking at an example program in the RKM p.252 under 
timer.device which explicitly sets the ReplyPort = NULL.  I needed an
example for setting the system time/date (RTClock broke on Jan 1 doncha
know - some programmers who write clock programs & dont know how to handle
year boundary conditions flames deleted)  Anyway I have been running this 
prog in my startup sequence to adjust the system date every boot.  It 
hasn't appeared to lead to any instability... or am i missing someting?

>
>-- 
>Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup


-Gary Brant		ARPA: brant@uf.msc.umn.edu


(My employer doesn't know about my ravings)