On 2016-07-08, Marius Gavrilescu <
mar...@ieval.ro> wrote:
> Consider the following one-line program:
>
> DO READ OUT #1
>
> When compiled, it gives no error. When run, it outputs the following on
> stderr:
>
> ICL129I PROGRAM HAS GOTTEN LOST
> ON THE WAY TO WHO KNOWS WHERE
> CORRECT SOURCE AND RESUBNIT
I thought ais523 would have answered by now... but nobody said anything, so
I decided to have a look myself.
I can certainly reproduce this:
# emerge dev-lang/c-intercal
$ echo 'DO READ OUT #1' > test.i
$ ick test.i
$ ./test
I
ICL129I PROGRAM HAS GOTTEN LOST
ON THE WAY TO WHO KNOWS WHERE
CORRECT SOURCE AND RESUBNIT
and I personally would have expected this output:
I
ICL633I PROGRAM FELL OFF THE EDGE
ON THE WAY TO THE NEW WORLD
CORRECT SOURCE AND RESUBNIT
this is what CLC-INTERCAL produces (well, it produces a *633 although the
message looks different) (and also except that you need to find some older
version of perl to use CLC-INTERCAL as there hasn't been any recent update)
(and yes I know, one of these years there may be a new CLC-INTERCAL; it
has been in the works for long enough) (sorry this paragraph starts looking
like LISP, PLEASE DON'T TRY THAT).
> This seems inconsistent with the manual -- shouldn't it be E633 instead?
> Am I missing something obvious or is this a bug?
I would think of it as a bug.
> It should be mentioned that a program where a NEXT statement points to
> a non-existent label does correctly give E129 during compilation.
>
> This is C-INTERCAL 0.29 from the Gentoo repos.
C