OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Makoto Iwamura (iwamuraPB.HIGHWAY.NE.JP)
Date: Wed Apr 04 2001 - 13:22:58 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Fergus Henderson wrote:
    >On 02-Apr-2001, Crispin Cowan <crispinwirex.com> wrote:
    >
    >> Ok. Assuming that <mark> is some kind of encoding such that protectec
    >> printf can determine whether it is there or not, and standard printf
    >> is not confused by <mark> being present, then this seems to have solved
    >> the 2-way compatibility problem. Now you're only stuck with the usual
    >> problems incurred by writing to the code segment :-)
    >>
    >> These would be:
    >>
    >> * Can't ROM the code. [...]
    >> * No recursion. [...]
    >> * Questionable reentrancy. [...]
    >
    >I think you misunderstood again. The mark is put in the code segment
    >at compile time. It is not modified at runtime. So it doesn't have
    >any of those problems that you mention.

    Yes, an argument count is decided and put in the code segument at
    the time when the calling function is compiled.

    Thanks for your answering instead of me. 

    --
Makoto Iwamura <iwamuramuraoka.info.waseda.ac.jp>
Muraoka Laboratory, Dept. of Information & Computer Science
Graduate School of Science & Engineering, Waseda University