From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2ccbce6c5ad05bfd X-Google-Attributes: gid103376,public From: Richard Riehle Subject: Re: Can OO be successful in real-time embedded systems? Date: 1996/05/09 Message-ID: #1/1 X-Deja-AN: 154027348 references: <3191DE76.130F@lmtas.lmco.com> content-type: TEXT/PLAIN; charset=US-ASCII organization: National University, San Diego mime-version: 1.0 newsgroups: comp.lang.ada Date: 1996-05-09T00:00:00+00:00 List-Id: Robert A Duff wrote: > > Run-time dispatching is just like a case-statement, except the branches > are scattered all over the code. To do white-box testing, you have to > track down all overridings of a given procedure. Having done that, it's > no harder than testing a case statement. So, I think you want a tool to > do that tracking down. I use "grep" for that purpose, but one could > imagine something more helpful. I am aware of the notion of dynamic case vis a vis dispatching. Also, the built-in safety of Ada 95 has not escaped my notice. However, in hard, real-time systems (HRTS), run-time dispatching is a little more of an issue than a simple case statement. The controlling factor is whether we can predict that a certain sequence of actions will be time-determinate. Granted, there will be many situations where this will be easily predicted. However, extensive use of run-time dispatching can, I believe, make it more difficult to predict the kind of timing requirements which often characterize HRTS software environents. Since Ada 95 is new, there is likely to be little experience with dispatching in HRTS. I am simply suggesting that it be approached conservatively. Perhaps I am just too much of a "scaredy-cat" about such things. However, I know I am not alone in this concern. Richard Riehle