Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!boulder!ub!dsinc!netnews.upenn.edu!weisen
From: weisen@eniac.seas.upenn.edu (Neil Weisenfeld)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: RCS for DOS
Message-ID: <28690@netnews.upenn.edu>
Date: 21 Aug 90 17:25:46 GMT
References: <TOM.90Aug21073135@hcx2.ssd.csd.harris.com>
Sender: news@netnews.upenn.edu
Reply-To: weisen@eniac.seas.upenn.edu (Neil Weisenfeld)
Organization: University of Pennsylvania
Lines: 24
In-reply-to: tom@ssd.csd.harris.com (Tom Horsley)

In article <TOM.90Aug21073135@hcx2.ssd.csd.harris.com>, tom@ssd (Tom Horsley) writes:
[stuff deleted]
>minor glitch last night. I tried out the $Header$ feature, using it
>to initialize a character string, and it generated a string containing
>a file name that looked like:
>
>    C:\PROGS\TESTING\RCS\fred.c
>
>needless to say, the back slash characters in the file name did not
>make it through to the actual string generated in the compiled program...
>

I've been using the $Id$ function instead to help overcome that problem.
It seems the same only without the leading components of the path
name.  

Another problem that I've had is that 'ident' doesn't seem to find any
i.d. strings in a binary file.  I've used a hex editor to ensure that
the data is there.  Any ideas?


Neil

P.S. -- Great thanks to the poster.