Hi, Graham - Nice work. > 3) Array and string parameter declaration syntax has merged into the > 2005 parameter declaration syntax. This is probably the right thing to do; P1800 has "string" as a "data_type" and I see that you have expanded value_range to handle strings; presumably there will be semantic restrictions on using (0:inf] for a string parameter, or {"nmos", "pmos"} for a real. On keywords, the document in mantis has "annex A" for the keywords; probably just a numbering issue with FrameMaker since you printed it by itself. > 6) It appears from the document formatting that all of the keywords > are to be contained on a single page. To maintain this constraint > the font size was substantially reduced when AMS keywords were added. > Should the single page format be maintained or restore the original > font size and have a 2 page list of keywords? The P1800 draft I have has 4 columns of keywords instead of 3; it looks like there's enough whitespace to do this here. > 8) Compiler directives and system task/functions has significant syntax. > Why is the syntax for constructs not documented in the syntax annex? Compiler directives are also missing from P1800's syntax annex. Wouldn't it be too much detail to specify the syntax for each system task/function in annex A? There are a lot of system tasks and functions. Also, while talking about system things, should the $ be part of the system_parameter_identifier, as it is part of the system_{task,function}_identifier? -GeoffreyReceived on Thu Sep 29 03:43:42 2005
This archive was generated by hypermail 2.1.8 : Thu Sep 29 2005 - 03:44:16 PDT