Hi Marcus,
I think the confusion is not on semantics, but on the discussion level. I
have absolutely no doubt that it is impossible to disable override of
global identifiers by local identifiers in Pike as it currently stands. I
fully agree with your reservations that this would create
Well, the context here is the language Pike, so please realize that
when talking about global identifiers, this refers to the Pike
concept of global identifiers, unless otherwise specified. And I will
assume that the same goes for when someone talks about classes and
signatures.
Perhaps. That's natural in old code that has been in production a long
time, otherwise the bug would have been found and fixed by now.
Another case is this from the Search module:
private mapping(string:int) query_profile_names = ([]);
/.../
void flush_profile(int p) {
I predict lots of warnings for mutex key objects in the future...
Good point. It would have to be restricted to either noncomplex types
or side-effect free initializations, I guess.
You mean people would feel forced to leave out the argument name just
to silence the compiler?
I can only see that happening for functions in interface classes that
defines some kind of callback, and that for some reason need to have a
(more or less) dummy body (the warning should of course be
We can have this discussion for 7.10. I'm tentatively against it.
I think we've had this discussion a while ago an decided agains
nameless parameters.
I'd rather have unused arguments become an optional warning in the
compiler than any other wierd workaround. That way, I can detect them
if I want to but for the most part just ignore them.
Hello,
Disclaimer:
I'm experiencing a bug in Caudium that makes Parser.HTML to crash.
Sorry, i wasn't able to reproduce it with a standalone Pike program due
to my lack of full understanding of entities handling in Parser.HTML.
There may be a bug in Caudium in this area i'd be happy to solve,
I really like getting warnings for non-argument unused variables.
10 matches
Mail list logo
