Re: How about only allowing stacked variables in functions

From: Adam Krolnik (adamk@cyrix.com)
Date: Sun Jan 04 1998 - 20:31:59 PST

  • Next message: Steve Meyer: "Suggestion for enhanced array of instance feature"

    >I suggest only allowing rentrant functions but not reentrant tasks.

    It's funny, I was thinking of asking this question.
    Why should we only allow reentrant tasks? Why not reentrant functions and remove the
    restriction that reentrant functions consume no simulation time.

    >other scheduling features of tasks. I looked at adding this to Cver

    Steve, I've heard the name "Cver" but never knew what it was, could you enlighten me?

    <p>>Adding rentrant (as an option?) variables to functions is easy and does
    >not cause scheduling problems because by definition functions are executed
    >instantaneously. Also it seems to me the various needs for more programming
    >langugage features can be solved by writing reentrant functions.

    I disagree; the specific feature if allowing simulation time to pass while using the task multiple times is what is really wanted. When I think about reentrant, I am thinking multiple
    processes will call a task that consumes time to perform its operation.

    On the subject of allowing reentrant functions. I have heard that functions can consume no time
    because otherwise you would have race conditions. With the addition of reentrant functions, this concern seems to be solved. Are there other reasons for restricting functions from consuming time?

    <p> Adam Krolnik
         Verification Engineer
         Cyrix - NSM.
         Richardson TX. 75085

    This archive was generated by hypermail 2.1.4 : Mon Jul 08 2002 - 12:52:33 PDT and
    sponsored by Boyd Technology, Inc.