On 03/10/2013 08:20 PM, Clinton Jeffery wrote:
> At link time, one would know if one had linked in an override of a built-in
> function, but you are right that at compile
> time, one doesn't know for sure so my suggestion was a warning. For that
> matter, I would suggest a warning for your
> redefinition of move(), since other code that you have linked to might be in
> for a nasty surprise if you redefine a
> built-in function in an incompatible way. But perhaps not everyone would like
> me warning them of likely bugs, so either
> I should not add more of them, or perhaps I should make it easy to turn them
> on or off.
I like the idea of turning them on and off. It'd be nice to get warnings about
redefinitions of functions,
but only when I want to see them! Despite the facetious example I gave, I do
sometimes redefine
functions as procedures, such as:
procedure system(cmd)
if \debug then write(cmd)
proc("system")(cmd)
end
--
Steve Wampler -- swamp...@noao.edu
The gods that smiled on your birth are now laughing out loud.
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group
