What should I put on stack?

[Antariy]

Nothing

[clive]

Note that the code is supposed to worked INLINE by the compiler. If used as designed nothing goes on the stack, and it works on the data in-place as it exists in the CALLERs frame of reference.

Convert it to a non-INLINE function and use pointers if you have to.

[Antariy]

Note that the code is supposed to worked INLINE by the compiler. If used as designed nothing goes on the stack, and it works on the data in-place as it exists in the CALLERs frame of reference.

Convert it to a non-INLINE function and use pointers if you have to.

Yes, that is point of my previous post (which currently contain "Nothing" word). After some thinking I decide, that explaining of this stuff would be longer than useful things which can be "extracted" from that information.

Using of pointers automatically require to convert the HLL code appropriatedly. Onan says what he wants to decrease work with HLL as much is possible. That is the reason to suggestion of references and C++ mode.



Alex

[Farabi]

Thanks alex  :U

[Antariy]

Thanks alex  :U

Clive right too - when you will compile the header as C++, you are needed to remove the "inline" specifier, otherwice object file would not contain the functions at all - it just "optimize-strip" them.
So, if you have something like:

Code Select Expand


inline int ReadObject(char *st, glObject *o){


you needed remove the "inline" that:

Code Select Expand


int ReadObject(char *st, glObject *o){


i.e. - just remove that word in text-editor.

The other possible way - do not use optimizations of inlineing (/Ob0 switch of command line of the compiler). I guess, this is much more simpler thing to "remove" inlineing.



Alex