On Mon, Apr 26, 2010 at 6:33 PM, Steve Schmechel wrote:

...

This file is not in any of the tarballs, including Nov2009. Do you have to generate it?

Yes, from http://monetdb.cvs.sourceforge.net/viewvc/monetdb/sql/src/server/sql_parser.mx?revision=1.334&view=markup

If you build a tarball from source, you should have it.

Maybe the tarballs only include bison's C output so bison isn't needed to build the tarballs. However, I'd say the Mx files from version control are the better way to understand the code anyway.

...

If so, that would be a horrible way to document an external API:

Feel free to write a good man page about how much of the standard is supported. I suspect the project authors would accept such a patch.

How much of the standard is supported is documented on [1], even though it may be too concise if you don't have the standard at hand. I think the problem is that [2] seems to be slightly outdated. What I'm wondering is that Mx is supposed to be a literate programming tool, allowing to intermingle code and documentation. For other parts of the online documentation, I could find the corresponding source files, but not for [2]. Wouldn't sql_parser.mx be a good place to put it, so it becomes easier to verify if it's current? Best regards, Isidor [1] http://monetdb.cwi.nl/SQL/Documentation/SQL-Features.html [2] http://monetdb.cwi.nl/SQL/Documentation/Queries.html