Path: utzoo!mnetor!tmsoft!torsqnt!jarvis.csri.toronto.edu!cs.utexas.edu!yale!venus!leichter
From: Leichter-Jerry@CS.YALE.EDU@venus.ycc.yale.edu
Newsgroups: comp.text.tex
Subject: Re: Typesetting programming languages -- RESULTS
Message-ID: <120.25efa0b7@venus.ycc.yale.edu>
Date: 3 Mar 90 15:47:19 GMT
References: <4354@jhunix.HCF.JHU.EDU>
Organization: Yale Computer Center (YCC)
Lines: 46

In article <4354@jhunix.HCF.JHU.EDU>, (Dan Barrett) writes:
> 	Thank you everybody who sent me suggestions on how to typeset
> programming languages (like C) in LaTeX.
> 
> 	The solution I chose is to use "tgrind".
> 
> 	I am not 100% happy with this solution, mainly because once you
> run something through tgrind, it is hard to edit later.  I'd really prefer
> a system that allowed me to do:
> 
> \begin{c_code}
> main()
> {
> 	int foo;
> 	...etc...
> }
> \end{c_code}
> 
> without all the muck that tgrind adds.  I suppose I could keep the C files
> separate, and write a program that runs them through tgrind, \inputs them
> into the LaTeX document, and runs LaTeX.
> 

Hmm, I'm sorry I didn't see this thread earlier.  Would you accept:

%[
{
	int foo;
	...etc...
}
%]

combined with a pre-processor that you have to feed the whole LaTeX file
through?  I modified tgrind some time back to do just that.  I've always
meant to change the name (so that people can distinguish the versions) and
really polish the thing up for general use, but it DOES work, quite reliably,
and is available to anyone who wants it by anonymous FTP from:

	VENUS.YCC.YALE.EDU, subdirectory [.TGRIND]

copy all the contents; if you are on a VMS system, you can copy a pre-built
TGRIND.EXE in BINARY mode.  Otherwise, re-build the thing yourself.

Sorry, NO mail distributions available - please don't ask.

							-- Jerry