digitalmars.D.learn - Shouldn't __FUNCTION__ return function name?
- Andrea Fontana (9/9) Jul 28 2015 Check this code:
- Steven Schveighoffer (8/16) Jul 28 2015 Be outside foreach. The way foreach works in many cases (including
- Andrea Fontana (3/11) Jul 28 2015 Too bad :|
Check this code: http://dpaste.dzfl.pl/a76db2cde13d When __FUNCTION__ is called inside a foreach body, it appears to be: f212.myFunction.__foreachbody1 Rather than: f212.myFunction. Is it correct? How can I get the function name?
Jul 28 2015
On 7/28/15 11:05 AM, Andrea Fontana wrote:Check this code: http://dpaste.dzfl.pl/a76db2cde13d When __FUNCTION__ is called inside a foreach body, it appears to be: f212.myFunction.__foreachbody1 Rather than: f212.myFunction. Is it correct?Yes.How can I get the function name?Be outside foreach. The way foreach works in many cases (including foreach over an associative array), is that the compiler constructs an internal function delegate, then passes it to a handler. See opApply and how it works. It's the same for AAs. http://dlang.org/statement.html#ForeachStatement -Steve
Jul 28 2015
On Tuesday, 28 July 2015 at 15:13:28 UTC, Steven Schveighoffer wrote:Too bad :|How can I get the function name?Be outside foreach. The way foreach works in many cases (including foreach over an associative array), is that the compiler constructs an internal function delegate, then passes it to a handler. See opApply and how it works. It's the same for AAs. http://dlang.org/statement.html#ForeachStatement -Steve
Jul 28 2015