Re: Help with Copying Shared Memory to Local

["martin.m.dowie" <martin.m.dowie@ntlworld.com>]

"Pat Rogers" <progers@classwide.com> wrote in message
news:aPwH8.15921$1U4.2841103386@newssvr30.news.prodigy.com...
> "John R. Strohm" <strohm@airmail.net> wrote in message
> news:EE1B58C60CD7D9ED.3DE0D594451AD094.92104DC9322C357A@lp.airnews.net...
> The other poster is right -- there's nothing to say that the above causes
the
> compiler to generate 16-bit accesses.  When you need that kind of control,
you
> are better off writing the machine-code insert to do it explicitly, rather
than
> trying to coerce the compiler to do it the way you want.  Sure, you can
often
> get your compiler to do what you want, until the next release!

Unless you have fixed your compiler at a particular version - not an
uncommon practice. Slap
a _huge_ comment about the potential non-portable nature of the code and
more detail in a
design document and most of us mere mortals would be happy.

(Quicker than finding someone with the right assembler skills too :-)