Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!aramis.rutgers.edu!athos.rutgers.edu!rbthomas From: rbthomas@athos.rutgers.edu (Rick Thomas) Newsgroups: comp.os.minix Subject: Re: The future of MINIX Message-ID: Date: 11 Jul 89 05:40:46 GMT References: <2835@ast.cs.vu.nl> <1989Jul8.171336.27399@sun.soe.clarkson.edu> <2851@ast.cs.vu.nl> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 24 > Conceivably I could also make a full cross > reference list and put in on the disk. Now, That's a good idea! Most people aren't interested in the Xref unless they are into serious code hacking anyway, so they can be expected to have the disks. Also, I bet it's easier to talk P-H into adding a disk to the distribution than adding 50-100 pages to the book. (Or printing a second volume with the code and Xref in it.) As an added benefit, if the Xref production can be automated (not easy, as Andy noted, but maybe some of the hackers out there would be willing to have a go at it. Warning -- you should probably start with the source code of the CPP and parser pass of the compiler. Anything less is bound to wind up getting confused by comments that look like code, etc.) The program that does it can be put on the floppy, instead of the actual Xref. Then people can have Xrefs of their own local versions. Rick -- Rick Thomas uucp: {ames, cbosgd, harvard, moss, seismo}!rutgers!jove.rutgers.edu!rbthomas arpa: rbthomas@JOVE.RUTGERS.EDU Phone: (201) 932-4301