Menu

HE Implementation

Mark
2010-09-02
2013-04-25
  • Mark

    Mark - 2010-09-02

    Hi,
    Can anyone help me to answer this question? I'm new to this project

    why does the implementation of HE do not include or reference to any CCL source?

    It seems to me that it was written completely separated.
    Thanks,
    Mark

     
  • Bill

    Bill - 2010-09-03

    Hi Mark,

         The HE does not use the CCL so that the CCL can be properly debugged. The concern was that if we used the CCL on both sides of the interface that an error may be masked, i.e. two wrongs make a right.

       -Bill-

     
  • Lance W. Durham

    Lance W. Durham - 2010-09-03

    Mark,

    The HE predated the CCL by a few years and was written using the old C-style CIGI API.  When we updated the HE to use CIGI 3, we simply updated the API's structures and functions.  We did this not out of laziness, but for the reasons Bill stated above.

    There was a technical limitation to consider, as well.  For the real-time version of the HE, the back end process runs in the RTX environment and any data allocated must reside in non-paged kernel memory.  This region of memory is not huge.  The C-style API is lighter-weight then the CCL partly because the former does not do cross-version translation.

    Lance

     
  • Mark

    Mark - 2010-09-07

    Thank you very much for answering my question (Bill and Lance). I understand now :)

     

Log in to post a comment.