|
![](/i/fill.gif) |
> The Turbo Pascal compiler also has many command-line options, and - I
> would suggest - *far* more error messages than the touch command. Not to
> mention a complete Pascal parser, AST manipulations, code generator,
> etc. Clearly it "should" be way, way bigger.
The article mentions the size of the main executable only (the editor).
It doesn't list all the associated .OVL (ancestors to .DLLs) and text
files it required, and the fact that the actual compiler was a separate
executable called by the IDE.
--
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/* flabreque */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/* @ */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/* gmail.com */}camera{orthographic location<6,1.25,-6>look_at a }
Post a reply to this message
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 02/11/2011 12:27 PM, Francois Labreque wrote:
>> The Turbo Pascal compiler also has many command-line options, and - I
>> would suggest - *far* more error messages than the touch command. Not to
>> mention a complete Pascal parser, AST manipulations, code generator,
>> etc. Clearly it "should" be way, way bigger.
>
> The article mentions the size of the main executable only (the editor).
> It doesn't list all the associated .OVL (ancestors to .DLLs) and text
> files it required, and the fact that the actual compiler was a separate
> executable called by the IDE.
The article doesn't seem to even *specify* exactly what it measured the
size of. Because, as you say, the Turbo Pascal environment definitely
consists of more than just one file...
Post a reply to this message
|
![](/i/fill.gif) |