<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
<br>
</div>Good idea but this seems difficult to do.<br>
In Olaf case it may be doable to spit out a better error message explicitely<br>
saying that "T" was considered as the "<language>" argument of PROJECT,<br>
because PROJECT is a builtin<br>
<br></blockquote><div>I was just agreeing with Olaf and stating a issue I ran into on error reporting when calling/using functions and macros. I don't have any solutions for him. Wish I did.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"></div>
<br>
In this case the MACRO CMake command has only "positional" arguments handling.<br>
So if you miss-use the ParseArguments macros the better you can do is enhance<br>
the ParseArguments macro in order to do a better job while checking<br>
its arguments.<br>
<br></blockquote><div><br>Yes the "positional" argument handling IMO is the problem. This leads to scouring code to determine what is wrong. It was as though the function that contained the parse arguments call did not exist. So the error reported had nothing to do with the real problem.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
May be the only way to have a better error reporting would be to have a new<br>
<br>
kwmacro(<name> KEYWORD <kw1> arg1 KEYWORD kw2 arg2 .... KEYWORD kwN argN)<br>
<br>
kwmacro(<name>)<br>
<br>
that would support keyword call instead of positional call.<br>
i.e.<br>
<br></blockquote></div><br>Named parameters may help, but the problem with the parser not recognizing (looking ahead for) the trailing paren and inferring missing parameters I believe is the root failure. Naming the arguments would aid in readability, but not fix the CMake parser. Maybe you are saying implementing named macros and changing the parser is the solution?<br clear="all">
<br>-- <br>Brian J. Davis<br><br>