Fortran to Lisp translation using f2cl
Software—Practice & Experience
API documentation from source code comments: a case study of Javadoc
SIGDOC '99 Proceedings of the 17th annual international conference on Computer documentation
A Formal Pattern Language for Refactoring of Lisp Programs
CSMR '02 Proceedings of the 6th European Conference on Software Maintenance and Reengineering
Converting call-by-reference to call-by-value: Fortran and Lisp coexisting
ISSAC '03 Proceedings of the 2003 international symposium on Symbolic and algebraic computation
Detection of Redundant Code Using R2D2
Software Quality Control
| Hi-index | 0.00 |
Modern software requirements are more diverse than before and can only be timely fulfilled via the extensive use of libraries. As a result, modern programmers spend a significant fraction of their time just mixing and matching these libraries. Programming language success becomes, then, more dependent on the quality and broadness of the accompanying libraries than on the language intrinsic characteristics. In spite of its recognized qualities, Common Lisp lags behind other languages as regards the quality and availability of its libraries. We argue that the best solution to overcome this problem is to automatically translate to Common Lisp the best libraries that are available in other languages. In this paper, we specifically address the translation of Java libraries using the Jnil translator tool and we provide a detailed explanation of the problems found and the lessons learned during the translation of a large Java library. Although many problems remain to be solved, the experiment proved the feasibility of the translation process and significantly increased our confidence in the future of Common Lisp.