<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://mw.hh.se/wg211/index.php?action=history&amp;feed=atom&amp;title=WG211%2FM20Zaytsev</id>
	<title>WG211/M20Zaytsev - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://mw.hh.se/wg211/index.php?action=history&amp;feed=atom&amp;title=WG211%2FM20Zaytsev"/>
	<link rel="alternate" type="text/html" href="http://mw.hh.se/wg211/index.php?title=WG211/M20Zaytsev&amp;action=history"/>
	<updated>2026-04-05T23:02:52Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.5</generator>
	<entry>
		<id>http://mw.hh.se/wg211/index.php?title=WG211/M20Zaytsev&amp;diff=2152&amp;oldid=prev</id>
		<title>Jacques: Created page with &quot;Title: BabyCOBOL: The Challenge to Program Generation Tool Developers  On one side of the gap we have academic researchers developing new techniques of language processing in...&quot;</title>
		<link rel="alternate" type="text/html" href="http://mw.hh.se/wg211/index.php?title=WG211/M20Zaytsev&amp;diff=2152&amp;oldid=prev"/>
		<updated>2020-02-04T19:00:28Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Title: BabyCOBOL: The Challenge to Program Generation Tool Developers  On one side of the gap we have academic researchers developing new techniques of language processing in...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Title: BabyCOBOL: The Challenge to Program Generation Tool Developers&lt;br /&gt;
&lt;br /&gt;
On one side of the gap we have academic researchers developing new&lt;br /&gt;
techniques of language processing in general and program generation in&lt;br /&gt;
particular, and validating them by prototyping tools that typically&lt;br /&gt;
work on one particular relatively well-designed language such as Java,&lt;br /&gt;
Scala, Scheme or ML, or a subset of such a language. On the other side&lt;br /&gt;
of the gap, we have industrial researchers and practitioners of the&lt;br /&gt;
same domain, struggling to implement tools that are capable of&lt;br /&gt;
processing legacy programming languages such as COBOL, FORTRAN, PL/I,&lt;br /&gt;
CLIST and 4GLs. Even those that wish this gap to be bridged,&lt;br /&gt;
understand that it is unfair to demand full coverage of monstrously&lt;br /&gt;
complex languages like COBOL from academics, and it is equally&lt;br /&gt;
unrealistic to expect all freshly developed techniques to be easily&lt;br /&gt;
portable to such languages without any help of the researchers. As a&lt;br /&gt;
bridge across this chasm, I will present BabyCOBOL: an artificially&lt;br /&gt;
created language of deliberately small size, with only a handful of&lt;br /&gt;
language features. Yet, each of the features it has, was inherited&lt;br /&gt;
from a similar feature from a legacy language such as COBOL, RPG, REXX&lt;br /&gt;
or a 4GL, and represents some compiler implementation problem,&lt;br /&gt;
well-known among legacy language-supporting tool vendors.&lt;br /&gt;
&lt;br /&gt;
BabyCOBOL is small enough to use as running example or an assignment&lt;br /&gt;
in a university course, if the goal is to produce engineers capable of&lt;br /&gt;
facing various problems of dealing with legacy languages. It is also&lt;br /&gt;
small enough to implement with limited resources within any framework&lt;br /&gt;
that is capable of tackling it, and yet demonstrate convincingly how&lt;br /&gt;
this framework helps the developer.&lt;/div&gt;</summary>
		<author><name>Jacques</name></author>
	</entry>
</feed>