|Q: flowgraphs and exceptions (newbie) Daniel.Vogelheim@post.rwth-aachen.de (1996-09-02)|
|Re: Q: flowgraphs and exceptions (newbie) email@example.com (Scott Stanchfield) (1996-09-03)|
|Re: Q: flowgraphs and exceptions (newbie) firstname.lastname@example.org (1996-09-03)|
|Re: Q: flowgraphs and exceptions (newbie) email@example.com (1996-09-05)|
|Re: Q: flowgraphs and exceptions (newbie) firstname.lastname@example.org (1996-09-05)|
|Re: Q: flowgraphs and exceptions (newbie) email@example.com (Scott Stanchfield) (1996-09-06)|
|From:||firstname.lastname@example.org (John Hagerman)|
|Date:||5 Sep 1996 23:54:41 -0400|
|Organization:||Carnegie Mellon University|
|Keywords:||errors, optimize, bibliography|
Daniel.Vogelheim@post.rwth-aachen.de (Daniel Vogelheim) writes:
> What are useful ways of representing (C++/Java-style) exceptions and
> their handlers in flowgraphs?
email@example.com (David Chase) writes:
> Asynchronous exceptions are more of a pain.
> I wrote a couple of articles for JCLT a few years back that attempted
> to explain this in gory detail (among other gory details).
Our moderator writes:
> [I don't know of any refs on this topic better than Chase's paper.
> Whatever you do, it's messy. -John]
Just curious, whether anyone in the compiler world has tried using a
key = "harel:88",
author = "David Harel",
title = "On Visual Formalisms",
journal = "Communications of the ACM",
volume = "31",
number = "5",
pages = "514-30",
month = "May",
year = "1988"
It's been tried for behavioral synthesis:
key = "gajski:etal:94",
author = "Daniel D. Gajski et al.",
title = "Specification and Design of Embeded Systems",
publisher = "PTR Prentice Hall",
year = "1994"
Return to the
Search the comp.compilers archives again.