Proceedings of the Eighth Israeli Conference on Computer Systems and Software Engineering
DOI: 10.1109/iccsse.1997.599883
|View full text |Cite
|
Sign up to set email alerts
|

Extension mechanisms in Montana

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
18
0

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 15 publications
(18 citation statements)
references
References 12 publications
0
18
0
Order By: Relevance
“…A prototype version of the IBM VisualAge C++ compiler [Nackman 1997;Soroker et al 1997] is used as the front end. The abstract syntax tree constructed by the front end is transformed into a PCG and a CFG for each function, which serve as input to the alias analyses.…”
Section: Methodsmentioning
confidence: 99%
“…A prototype version of the IBM VisualAge C++ compiler [Nackman 1997;Soroker et al 1997] is used as the front end. The abstract syntax tree constructed by the front end is transformed into a PCG and a CFG for each function, which serve as input to the alias analyses.…”
Section: Methodsmentioning
confidence: 99%
“…Since extensions are written in C++ and have write access to the internals, they can crash Montana. Montana assumes that writers of extensions "know what they are doing" [28].…”
Section: Figure 1 Component With Apimentioning
confidence: 99%
“…In contrast, the evolution of the observer extension in Montana were driven by tool building. Observer extension in Montana have been incrementally added and refined as requested by tool builders: "Instead of guessing all of the distinguished points for observation, we added observers as needed" [28].…”
Section: Component Evolutionmentioning
confidence: 99%
“…However, JikesRVM does not offer a general facility to store and retrieve metadata, and all tools making use of the data must strictly be written within the JikesRVM framework. Similarly, Montana and Oberon provide frameworks for building tools and sharing information within the software development toolchain [18,10]. In both cases, plug-ins must be written specifically to the API of the system.…”
Section: Related Workmentioning
confidence: 99%