kenneth wrote:
>
> Please see:
>
> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?AlternativeNamedParameterSyntax
...
> 2 -- All those '$' characters are confusing (see flowsnake.ngc in nc_files
> in HEAD for the example).
...
> 2 -- I took part of this comment to mean that the '$' characters are ugly.
> Because they are so blocky, they catch the eye and make the code harder to
> read (for a human). I had originally wanted to use [] characters, but
> (someone else) noticed that #[sqrt[#1]] is legal syntax. That would have
> required more lookahead in the parser than is currently supported. The
> alternative uses <>, instead.
i'm not terribly familiar with the g-code language, and so i'm
not sure about the parsing constraints. but having looked at the
flowsnake example: would it be possible to make the bracketing
characters optional, only requiring them in the cases where
they're needed for disambiguation? i realize this makes the
parser more complicated, but it would clearly clean up the syntax
quite a bit if it could be done.
(for a familiar example where this kind of dual-syntax paradigm
works well, consider the bourne shell, where $a and ${a} are
identical semantically, but not syntacticaly.)
paul
=---------------------
paul fox, [EMAIL PROTECTED] (arlington, ma, where it's 28.0 degrees)
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
