Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.7.0.10 $; site okstate.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!okstate.UUCP!gregg
From: gregg@okstate.UUCP
Newsgroups: net.sources.games
Subject: Re: pm help needed
Message-ID: <47500002@okstate.UUCP>
Date: Wed, 8-Jan-86 12:40:00 EST
Article-I.D.: okstate.47500002
Posted: Wed Jan  8 12:40:00 1986
Date-Received: Fri, 10-Jan-86 05:27:16 EST
References: <228@sdcc7.UUCP>
Lines: 17
Nf-ID: #R:sdcc7.UUCP:228:okstate.UUCP:47500002:000:776
Nf-From: okstate.UUCP!gregg    Jan  8 11:40:00 1986


    It turns out that the problem is not so much ordering as it is the use
of the CVT instruction.  By convention, only LONG WORDS are placed on the
stack, so when chars, or shorts are passed to functions, they are first
converted to longs before being placed on the stack.  On the function end,
CVT is again useed to convert (if needed) the long word on the stack to the
type of the argument as specified by the declaration of the parameter.  This
effectively gives you the problems that you find when INTS are passed to CHARS,
or any other combination of different types.


Gregg Wonderly
Department of Computing and Information Sciences
Oklahoma State University

UUCP: {cbosgd, ea, ihnp4, isucs1, mcvax, uokvax}!okstate!gregg
ARPA:  gregg%okstate.csnet@csnet-relay.arpa