From: Raymond T. <toy...@gm...> - 2011-03-09 19:39:42
|
On 3/9/11 2:29 PM, Sam Steingold wrote: >> * Raymond Toy <gbl.enlzbaq@tznvy.pbz> [2011-03-09 13:08:16 -0500]: >> >>>> In addition, I'd like the keyword extension enabled. >>> I don't think this is a good idea. >>> I used to use that with cvs but not with mercurial. >>> http://mercurial.selenic.com/wiki/KeywordPlan#head-2007fad6f31bf6f1f1b5c3d5b02e5c6225de3ec5 >>> http://mercurial.selenic.com/wiki/VersioningWithMake >>> >> Yes, I read those. But f2cl doesn't use make, but expects the files >> to contain $Id$ keywords. > that made sense for cvs because each file had its own id. > with mercurial it makes no sense whatsoever. > just put a single > > (defvar *id* (shell "hg id --debug")) > > in one file and you already have full information. Perhaps, but I don't want to write a portable shell for every Lisp. Right now, f2cl can be run by any (I think) common lisp. I already added the keyword extension locally and the generated Id's are different: src/f2cl/src/f2cl1.l:20: "$Id: f2cl1.l,v e2000d02dd2a 2010/10/08 03:05:30 rtoy $") src/f2cl/src/f2cl2.l:24: "$Id: f2cl2.l,v ee10069a0482 2008/02/22 22:19:34 rtoy $") src/f2cl/src/f2cl3.l:28: "$Id: f2cl3.l,v ee10069a0482 2008/02/22 22:19:34 rtoy $") src/f2cl/src/f2cl4.l:17: "$Id: f2cl4.l,v ee10069a0482 2008/02/22 22:19:34 rtoy $") src/f2cl/src/f2cl5.l:53: "$Id: f2cl5.l,v f82a7b97eeed 2010/02/23 05:21:30 rtoy $") src/f2cl/src/f2cl6.l:31: "$Id: f2cl6.l,v e4ea90ad64ff 2008/08/24 00:56:27 rtoy $") src/f2cl/src/macros.l:9: "$Id: macros.l,v 1ba3edd71647 2011/02/28 22:21:07 rtoy $") This is rather nice to know for debugging purposes when an conversion was done that is now broken but used to work. It makes it easy to begin locating where the bug was introduced. Of course, I could use hg blame to figure this out, but Id's and dates are useful information to start with. And yes, I could use a local .hgrc to enable the extension, but I don't want to have to remember that on every machine I use and I want other users of f2cl to be able to see the keywords to help me debug issues. Ray |