🚀 go-pugleaf

In article <3653A950.30D9@well.com> shiva@well.com "Ken" writes:

>[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.

It would probably have been worth splitting your article up since it
consists of unrelated parts. For example this question is inappropriate
for comp.lang.c.

>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?

Declaration specifiers are allowed to appear in any order. However it is
good practice to put storage class specifiers (static, register, typedef
etc.) first. Indeed the current C standard deprecates any other use. This
is why the compiler warns you about this (but doesn't refuse to compile).
A C compiler is allowed to warn about anything it likes as long as it
still compiles valid programs.

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

chars are allowed to be used as array indexes but gcc has apparently
chosen to warn you about such use because plain char can be signed or
unsigned on different implementations. This could trip up the unwary.
You'd be better off using something like unsigned char for this sort
of thing and I believe gcc won't complain about that.

-- 
-----------------------------------------
Lawrence Kirby | fred@genesis.demon.co.uk
Wilts, England | 70734.126@compuserve.com
-----------------------------------------