🚀 go-pugleaf

[g21k is DOS-based Gnu C 2.3.3 targeted for Analog Devices SHARC 21000
architecture.]

I'm compiling in a DOS window under OS/2, specifically Warp 4 with
fixpak 8. After a few modules compile, the whole system crashes to a
register screen. It's not related to a specific source module, as
following a reboot, the Make will resume, go for a few more modules, and
crash again. Anyone seen this? It's most likely IBM's fault, but I don't
have a good idea on how to narrow it down for a bug report or
workaround. I suppose I'll have to start doing my compiles under NT and
hope it works a little better.

Also, I've inherited an idiom that looks like this:

[in header]
#define LOCAL_LINKAGE
#define near
#define local_proc static near LOCAL_LINKAGE

[in .c file]
int local_proc foo (int arg) { ... }

g21k warns about "static" not being at the beginning of the declaration.
Does standard C not allow "static" (a property of the function, not the
return type) to be sytacticly adjacent to the function name?

I've also seen warnings about an array index being of type char. Why
should it care?

Is there a way to silence these warnings?

-- 
Ken
mailto:shiva@well.com
http://www.well.com/user/shiva/
http://sewnsurf.home.ml.org/
http://www.e-scrub.com/cgi-bin/wpoison/wpoison.cgi (Death to Spam!)