Xref: utzoo alt.folklore.computers:3229 comp.lang.misc:4971
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!rutgers!cbmvax!snark!eric
From: eric@snark.uu.net (Eric S. Raymond)
Newsgroups: alt.folklore.computers,comp.lang.misc
Subject: INTERCAL (was: Re: Hacker's Dictionary)
Message-ID: <1WLjdS#5Tk5sy7yFvVx0SVRDv7mPbXT=eric@snark.uu.net>
Date: 5 May 90 14:21:22 GMT
References: <1990Apr25.100454.25726@lth.se>
Followup-To: poster
Lines: 16

> I think implementing INTERCAL would not only be an extremely difficult,
> But, where shall we find a description ? how shall we write it ? lex/yacc ?
> C coding by hand ? Shouldn't we also create comp.lang.INTERCAL ?

Over the last two days, I have written most of an INTERCAL-to-C compiler
using YACC and LEX. It wasn't hard. But then I'm...uh...pretty good with
YACC and LEX.

This is not a joke. (Well, INTERCAL is a joke. This announcement isn't).

Anybody wanna write a storage-management system for the INTERCAL storage
model, or a set of output functions for butchered Roman numerals? That's
about all this puppy needs to be usable. Or, at any rate, as usable as
INTERCAL is going to get...
-- 
      Eric S. Raymond = ...!uunet!snark!eric  (mad mastermind of TMN-Netnews)