Bild von Institut mit Unilogo
home uni uni suche suche sitemap sitemap kontakt kontakt
unilogo Universität Stuttgart

Programmiersprachen und Übersetzerbau : Veröffentlichungen

Bibliographie 1996 BibTeX

englishicon
 
@inproceedings {INPROC-1996-26,
   author = {Wolfgang Gellerich and Michael M. Gutzmann},
   title = {{Massively Parallel Programming Languages - A Classification of Design Approaches}},
   booktitle = {Proceedings of the ISCA International Conference on Parallel and Distributed Computing Systems 1996, Vol. I},
   publisher = {ISCA in Cooperation with IEEE Computer Society},
   institution = {Universit{\"a}t Stuttgart, Fakult{\"a}t Informatik, Elektrotechnik und Informationstechnik, Germany},
   pages = {110--118},
   type = {Konferenz-Beitrag},
   month = {Dezember},
   year = {1996},
   keywords = {Programming Languages; Parallel Programming},
   language = {Englisch},
   cr-category = {D.1.3 Concurrent Programming,     D.2 Software Engineering,     D.3.2 Programming Language Classifications},
   department = {Universit{\"a}t Stuttgart, Institut f{\"u}r Softwaretechnologie, Programmiersprachen und {\"U}bersetzerbau},
   abstract = {This paper presents the result of a study in which we examined about 50 massively parallel programming languages in order to detect typical approaches towards supporting parallelism. Based on classification into nine classes, semantic properties affeccting the development of parallel programs are compared. From a consideration of the general function of programming languages in software engineering, we derive basic requirements on parallel languages.},
   url = {http://www2.informatik.uni-stuttgart.de/cgi-bin/NCSTRL/NCSTRL_view.pl?id=INPROC-1996-26&engl=0}
}
@inproceedings {INPROC-1996-25,
   author = {Bernd Holzm{\"u}ller},
   title = {{Extending the Object-Orientedness of Ada95}},
   booktitle = {Proceedings of the 1996 Ada-Europe International Conference on Reliable Software Technologies},
   publisher = {Springer Berlin Heidelberg},
   institution = {Universit{\"a}t Stuttgart, Fakult{\"a}t Informatik, Elektrotechnik und Informationstechnik, Germany},
   series = {Lecture Notes in Computer Science},
   volume = {1088},
   pages = {357--369},
   type = {Konferenz-Beitrag},
   month = {April},
   year = {1996},
   isbn = {978-3-540-61317-6},
   isbn = {"ISSN: "ISSN: 0302-9743 (Print) 1611-3349 (Online)"},
   isbn = {"DOI:10.1007/BFb0013502"},
   keywords = {Languages; Ada95; Object Oriented},
   language = {Englisch},
   cr-category = {D.3.2 Programming Language Classifications,     F.3.3 Studies of Program Constructs},
   department = {Universit{\"a}t Stuttgart, Institut f{\"u}r Softwaretechnologie, Programmiersprachen und {\"U}bersetzerbau},
   abstract = {In the object-oriented extension of Ada95 some constructs and connected type rules have been introduced that restrict the flexibility in using the whole set of features the object-oriented paradigm provides. Especially the introduction of tagged types leads to a loss of potential reuse if efficiency is of concern while the rules connected with dispatching disable full static type checking for subprogram calls. A closer investigation of these constructs and constraints reveals that some of them are completely unnecessary and some could be relaxed with minor changes of the language. With corresponding modifications, the language gains additional flexibility and becomes easier to use, while, through the introduction of multi-methods, the language regains the property of being statically type-safe.},
   url = {http://www2.informatik.uni-stuttgart.de/cgi-bin/NCSTRL/NCSTRL_view.pl?id=INPROC-1996-25&engl=0}
}
@inproceedings {INPROC-1996-24,
   author = {Wolfgang Gellerich and Markus Kosiol and Erhard Pl{\"o}dereder},
   title = {{Where does GOTO go to?}},
   booktitle = {Proceedings of the 1996 Ada-Europe International Conference on Reliable Software Technologies},
   publisher = {Springer Berlin Heidelberg},
   institution = {Universit{\"a}t Stuttgart, Fakult{\"a}t Informatik, Elektrotechnik und Informationstechnik, Germany},
   series = {Lecture Notes in Computer Science},
   volume = {1088},
   pages = {385--395},
   type = {Konferenz-Beitrag},
   month = {April},
   year = {1996},
   isbn = {978-3-540-61317-6},
   isbn = {"ISSN: 0302-9743 (Print) 1611-3349 (Online)"},
   isbn = {"DOI: 10.1007/BFb0013504"},
   keywords = {Languages; Ada95; Efficiency},
   language = {Englisch},
   cr-category = {F.3.1 Specifying and Verifying and Reasoning about Programs},
   department = {Universit{\"a}t Stuttgart, Institut f{\"u}r Softwaretechnologie, Programmiersprachen und {\"U}bersetzerbau},
   abstract = {Although GOTO has long been criticized for being 'unstructured' and causing 'unreliable' programs, it is still in use and even modern languages like Ada95 provide GOTO. Why? This paper presents the results of a study in which we examined 316 MB of Ada source code in order to find the frequency and typical applications of GOTO. It turned out that about 99\% of all examined files do not contain any GOTO, but we also found {\ss}paghetti code``, generally justified by efficiency arguments. We analyzed whether GOTO really improved efficiency and examined sources containing GOTO by code inspection in order to determine its typical applications.},
   url = {http://www2.informatik.uni-stuttgart.de/cgi-bin/NCSTRL/NCSTRL_view.pl?id=INPROC-1996-24&engl=0}
}
@inbook {INBOOK-1996-03,
   author = {Rainer Koschke and Erhard Pl{\"o}dereder},
   title = {{Ans{\"a}tze des Programmverstehens}},
   series = {Softwarewartung und Reengineering - Erfahrungen und Entwicklungen},
   publisher = {Deutscher Universit{\"a}ts-Verlag},
   pages = {159--176},
   type = {Beitrag in Buch},
   month = {Dezember},
   year = {1996},
   keywords = {Reengineering; Softwarewartung},
   language = {Deutsch},
   cr-category = {D.2 Software Engineering},
   department = {Universit{\"a}t Stuttgart, Institut f{\"u}r Softwaretechnologie, Programmiersprachen und {\"U}bersetzerbau},
   abstract = {Programmverstehen ist der Proze{\ss} des Wissenserwerbs {\"u}ber ein Computerprogramm. E s ist die Voraussetzung f{\"u}r Fehlersuche, Erweiterung, Wiederverwendung und Dokumentation. Eine Reihe von Ans{\"a}tzen versucht, das Programmverstehen maschinell zu unterst{\"u}tzen. Die gegenw{\"a}rtigen Ans{\"a}tze werden in diesem Artikel klassifiziert in grundlegende und wissensbasierte Analysen. Grundlegende Analysen verf{\"u}gen {\"u}ber kein Wissen {\"u}ber die Anwendung und allgemeine Programmierung; sie basieren lediglich auf Programmiersprachensyntax und -semantik. Sie lassen sich weiter gliedern in grundlegende statische und dynamische Analysen, abh{\"a}ngig davon, ob sie zur {\"U}bersetzungszeit oder zur Laufzeit vorgenommen werden. Wissensbasierte Analysen verf{\"u}gen {\"u}ber Anwendungswissen und allgemeines Programmierwissen. Sie lassen sich unterscheiden in Parsing-Ans{\"a}tze, die sich ausschlie{\ss}lich auf formale und strukturelle Programmeigenschaften st{\"u}tzen, und informelles Schlie{\ss}en, welches dar{\"u}ber hinaus auch noch informelle Information in Betracht zieht. Der Artikel gibt Beispiele zu den verschiedenen Analyseformen.},
   url = {http://www2.informatik.uni-stuttgart.de/cgi-bin/NCSTRL/NCSTRL_view.pl?id=INBOOK-1996-03&engl=0}
}