Date: Tue, 4 Feb 1997 15:01:08 +0200 (IST) From: Eli Zaretskii To: Robert Hoehne cc: DJGPP workers Subject: Re: GNU ID Utils ported to DJGPP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 4 Feb 1997, Robert Hoehne wrote: > At first I want to say, that this is really a good tool. Yes, amazing, right? > At first mkid does not give any message if I select a not supported > language. This is probably a bug in the original sources and not > in the port. This is a feature; it is documented in the id-utils on-line docs: any files for which there's no scanner defined are ignored. I think you are supposed to edit the file share/id-lang.map to make `mkid' recognize additional extensions (if they can be parsed by one of the scanners built into id-utils), or write your own scanner (if none of the scanners will do the job). I already added a couple of extensions (such as .txh) there. Aren't the languages supported by `mkid' by default enough to tag DJGPP library sources? It supports C, C++ and assembly, so what else do we need? > mkid -i c Why not just "mkid"? Why did you need "-i c"? > it does at first not complain the wrong language (see above) and > after a while it prints something like "nothing to do" and the > current directory is now %DJDIR%/src/libc/stubs !!! I was lazy and didn't make `mkid' restore its original directory when it exits abnormally. I thought the problem isn't visible when mkid exits normally, but your case seems to indicate otherwise. I will see why. Note that a nasty side effect of the current port is that if you run `mkid' on a different drive, the current directory on that drive changes, even if `mkid' exits normally. For example, try this: cd c:\ d: mkid c:/djgpp/src/libc c: cd The last CD will print something other than C:\. (Now you see why I got lazy? You need to restore the original directory on other drives also! `find' and `rm' do restore it as appropriate, but it was a non-trivial task to accomplish, so I thought I could avoid it this time; I guess I was wrong...) Anyway, thanks for the input.