Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!ncar!tank!eecae!netnews.upenn.edu!kings.wharton.upenn.edu!lau From: lau@kings.wharton.upenn.edu (Yan K. Lau) Newsgroups: comp.sys.apollo Subject: Discrepancy in sio.h file? Message-ID: <12447@netnews.upenn.edu> Date: 27 Jun 89 16:30:51 GMT Sender: news@netnews.upenn.edu Reply-To: lau@kings.wharton.upenn.edu (Yan K. Lau) Distribution: na Organization: Otto's Bay Lines: 54 This is a technical question about the C compiler and the Apollo sio include file. There seems to be a discrepancy between parameter lists. In /usr/apollo/include/sio.h, the sio_$control call is defined as follows: extern void sio_$control( stream_$id_t &stream_id, sio_$opt_t &option, void &value, status_$t *status ); BTW, In /sys/ins/sio.ins.c, the call is defined simply as: std_$call void sio_$control(); In comparison, in /sys/ins/sio.ins.pas, the call is defined as: PROCEDURE sio_$control(IN strid: stream_$id_t; IN option: sio_$opt_t; IN value: UNIV sio_$value_t; OUT status: status_$t); EXTERN; The _Domain/OS Call Reference_, defines the call as follows: extern void sio_$control( stream_$id_t &stream_id, sio_$opt_t &option, sio_$value_t &value, status_$t *status ); The definition of sio_$value_t is: typedef union { char c; pinteger i; char b; /* boolean */ sio_$err_enables_t es; } sio_$value_t; It appears that the third parameter in /usr/apollo/include/sio.h is wrong. Is this true? If so, what other "gotchas" are out there? This gives me an uneasy feeling. Has anyone else encounter similar problems? Yan. --- Yan K. Lau + the last message of a newgroup will be: )~ + a) longer than one screen & ~/~ lau@scrolls.wharton.upenn.edu + b) something you're not interested in. /\ University of Pennsylvania + your decision, 'n' key or space bar?