Related articles |
---|
Q: flowgraphs and exceptions (newbie) Daniel.Vogelheim@post.rwth-aachen.de (1996-09-02) |
Re: Q: flowgraphs and exceptions (newbie) scooter@mccabe.com (Scott Stanchfield) (1996-09-03) |
Re: Q: flowgraphs and exceptions (newbie) chase@centerline.com (1996-09-03) |
Re: Q: flowgraphs and exceptions (newbie) hagerman@ece.cmu.edu (1996-09-05) |
Re: Q: flowgraphs and exceptions (newbie) kanze@lts.sel.alcatel.de (1996-09-05) |
Re: Q: flowgraphs and exceptions (newbie) scooter@mccabe.com (Scott Stanchfield) (1996-09-06) |
From: | hagerman@ece.cmu.edu (John Hagerman) |
Newsgroups: | comp.compilers |
Date: | 5 Sep 1996 23:54:41 -0400 |
Organization: | Carnegie Mellon University |
References: | 96-09-009 96-09-017 |
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?
chase@centerline.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
StateChart-like representation:
@Article{harel:88,
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:
@Book{gajski:etal:94,
key = "gajski:etal:94",
author = "Daniel D. Gajski et al.",
title = "Specification and Design of Embeded Systems",
publisher = "PTR Prentice Hall",
year = "1994"
}
~ John
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.