Hi Nikhil --
Referring to a paren-ful function without parens is legal, as it is the
way to effectively get the Chapel equivalent of a function pointer (see
doc/[release/]technotes/README.firstClassFns for details). Obviously, it
should not trigger an internal error, though and we're trying to clamp
down on these, so thanks for reporting it.
In this case, it should arguably be a no-op, or to potentially generate a
warning for being a no-op where perhaps you simply forgot your parens.
Thanks again for the bug report and pull request,
-Brad
On Wed, 24 Jun 2015, Nikhil Padmanabhan wrote:
Hi,
If I define a procedure with parens, and then try to call it without parens, I
get a chapel internal error EXP0351 (running on the current version of master
cb401b3), instead of a syntax error. Not an issue, but wanted to flag the
internal error.
See :
https://github.com/npadmana/chapel/tree/npbug_noparens_call/test/users/npadmana/bugs/noparens_call
<https://github.com/npadmana/chapel/tree/npbug_noparens_call/test/users/npadmana/bugs/noparens_call>
for a trivial test case (although I haven’t figured out how to have this work
under the test framework, hence the notest).
— Nikhil
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
Chapel-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-bugs
