|
From: Robert W. <rj...@du...> - 2005-03-06 19:28:32
|
> I'm getting '?' characters instead of hypens when words are split. Huh. Works OK for me. Might be something to do with your LANG variable? Mine is en_US. I've seen man mess up royally before when it was set to something else like en_US.UTF-8. > My main comment is that I wouldn't have given nearly as much detail. I=20 > would have just given the basics and then pointed at the user manual. I=20 > definitely wouldn't have described the debugging options. That was the original idea. Then I realized that 1) we don't have any HTML documentation of a lot of those options anyway; 2) I could never remember the syntax of the more obscure options (like, say, --trace-codegen) and searching for it in the HTML and source code was a pain. So I thought it would be a good idea to get all the options gathered together in one place. > I'm just=20 > worried about double maintenance. (It would be nice to auto-generate the=20 > man page from the manual section describing the command line args.) > But I don't want to be too negative, it's good to have a man page. Double maintenance is a problem, for sure, and the auto-generate idea crossed my mind more than once while I was doing this. Maybe the source code should be the golden source for all of this, with a perl script that strips the documentation and generates the options parts of the man page and HTML documentation? Like javadoc does for java. That way there's plenty of examples scattered around you when you add a new option. Any thoughts? Probably this shouldn't hold up 2.4.0, but it would be nice to have it for 3.0.0. Regards, Robert. --=20 Robert Walsh Amalgamated Durables, Inc. - "We don't make the things you buy." Email: rj...@du... |