🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.text.tex
Article #10409

dvicopy on NeXT

#10409
From: Danny Quah
Date: Sun, 23 Jun 1991 00:05
52 lines
2725 bytes
[]


Sometime back I asked about printing dvi files that used .vf's on non-
Postscript printers.  I got a very helpful note on this from Don Hosek
(part of his article for a TUG meeting).  So, I went and got dvicopy
from ymir and tried to compile it on my NeXT (The dvicopy I got
identifies itself as version 1.2).

	Since I don't have a Pascal compiler, I fed the .p file output
from tangle on dvicopy.web to p2c, after setting random_reading to
false in dvicopy.web.

	(BTW, if Peter Breitenlohner and Dave Gillespie are out there:

1.~When random_reading is set to false, could dvicopy.web emit Pascal
code not just _not_ to call dvilength () and dvimove (), but also in
the definitions of those functions, not even try to grab setpos~() and
curpos~()?  /bin/ld on my NeXT barfs at those, /bin/ld never looks
ahead to see that these things are never actually required.  But
perhaps I just don't know that it can't be done in Pascal...  I went
in by hand and #ifdef'ed those to null functions.)

2.~"case others" doesn't get translated right. Should this be going
directly to "default"?  (I'm assuming, but I can't understand how if
this is standard Pascal output, p2c users haven't already picked this
up.)

3.~(Possibly another in the category of "How come p2c did this?")  Why
is there a call to RESETBUF () in inputln ()?  It's not obvious to me
from the Pascal code why it's required, and again, I can't see that it
preprocesses correctly to proper C.  (gcc dies here as well so I'm not
the only one, I guess.)

	I have p2c version 1.19, picked up scant hours ago from
cs.orst.

	Now, dvicopy compiles and ld's fine, but does a Segmentation
fault upon execution.  I tried to run it under gdb, whereupon I get
4500+ messages of error on my_memmove ().

	Has anyone out there compiled dvicopy on a NeXT?  I apologize
if these are obvious errors on my part, I haven't been able to go
through dvicopy.dvi as throughly as I would have liked.  If you feel
these aren't of general interest, just email me.  I'm happy to
summarize.

--
--Danny (dquah@athena.mit.edu, dquah@dolphin.mit.edu)
Dept. of Economics MIT, E52-274b, Cambridge MA 02139
Voice: (617) 253-0914 Fax: (617) 253-1330
#
Technical Details
Message-ID: <1991Jun23.000508.27842@athena.mit.edu>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!mintaka!bloom-picayune.mit.edu!athena.mit.edu!dquah

Show Full Headers
Complete Article Headers
Newsgroups: comp.text.tex,comp.sys.next
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!mintaka!bloom-picayune.mit.edu!athena.mit.edu!dquah
From: dquah@athena.mit.edu (Danny Quah)
Subject: dvicopy on NeXT
Message-ID: <1991Jun23.000508.27842@athena.mit.edu>
Summary: dvicopy faults Segmentation
Keywords: p2c, dvicopy, NeXT
Sender: news@athena.mit.edu (News system)
Organization: Massachusetts Institute of Technology
Date: Sun, 23 Jun 91 00:05:08 GMT
Lines: 52