This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Cracking the 500-Language Problem
November/December 2001 (vol. 18 no. 6)
pp. 78-88
ASCII Text
x 
 
Ralf Lämmel, Chris Verhoef, "Cracking the 500-Language Problem," IEEE Software, vol. 18, no. 6, pp. 78-88, November/December, 2001.
 
 
BibTex
x
 
@article{ 10.1109/52.965809,
author = {Ralf Lämmel and Chris Verhoef},
title = {Cracking the 500-Language Problem},
journal ={IEEE Software},
volume = {18},
number = {6},
issn = {0740-7459},
year = {2001},
pages = {78-88},
doi = {http://doi.ieeecomputersociety.org/10.1109/52.965809},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Cracking the 500-Language Problem
IS - 6
SN - 0740-7459
SP78
EP88
EPD - 78-88
A1 - Ralf Lämmel,
A1 - Chris Verhoef,
PY - 2001
VL - 18
JA - IEEE Software
ER -
 
Constructing analysis and modification tools for software assets is laborious because you first need to implement the underlying parser for the software's specific programming language. These implementations are generally not in the public domain. So, parser development for any of the 500+ languages in use today implies a major up-front investment. The authors propose a solution that will work for virtually all languages: the rapid development of renovation parsers by stealing the grammars. They also share lessons learned.
Citation:
Ralf Lämmel, Chris Verhoef, "Cracking the 500-Language Problem," IEEE Software, vol. 18, no. 6, pp. 78-88, Nov.-Dec. 2001, doi:10.1109/52.965809
Usage of this product signifies your acceptance of the Terms of Use.