Mail Archives: djgpp/1994/12/15/23:23:16
>I have some C which I am (cross)compiling which generates some global
>data declarations. The order of this data is important to me and I am
>having some trouble getting the compiler to leave it in the order in
>which it is declared.
Why, pray tell, _is_ the order so important? One presumes that the
data are somehow related, in which case it might be better to put
them in a struct. AFAIK, structs are non-rearrangeable.
--- Aaron Ucko (ucko AT vax1 DOT rockhurst DOT edu; finger for PGP public key) -=- httyp!
-=*=-Just because you're paranoid doesn't mean they aren't out to get you.-=*=-
Geek code 2.1 [finger hayden AT vax1 DOT mankato DOT msus DOT edu for explanation]:
GCS/M/S d(-) H s g+ p? !au a-- w+ v+ C++(+++)>++++ UL++(-)(S+)>++++ P++
L+(++) 3(-) E-(----) !N>++ K- W-(---) M-(--) V(--) po-(--) Y+(++) t(+) !5 j R
G tv--(-) b+++ !D(--) B--(---) e>++++(*) u++(@) h!() f(+) r-(--)>+++ n+(-) y?
t fine!
In a DOS session, the new long file name calls are just simple DOS
interrupts (see Ralf Brown's interrupt list) which makes long names easy to
implement. Other Win 95 features are not accessible this easily, sorry.
It would even be theoretically possible to support long names on
Pre-Win 95 systems with a TSR or device driver.
- Raw text -