1. namespace bug?
- Posted by useless Apr 03, 2009
- 1010 views
- Last edited Apr 04, 2009
I just heard a rumour that a user function name which is the same name as a builtin name will clash even if namespacing is used to clarify which function is being specified. Then i heard people knew about it, and voted to allow this to continue. And people who knew about it kept it hushed up.
Are the rumours correct?
useless
2. Re: namespace bug?
- Posted by CoJaBo Apr 03, 2009
- 1009 views
- Last edited Apr 04, 2009
This is one case that triggers a warning on perfectly valid code just by adding an include:
include std/map.e ?compare(1,0)
3. Re: namespace bug?
- Posted by DerekParnell (admin) Apr 03, 2009
- 997 views
- Last edited Apr 04, 2009
I just heard a rumour that a user function name which is the same name as a builtin name will clash even if namespacing is used to clarify which function is being specified. Then i heard people knew about it, and voted to allow this to continue. And people who knew about it kept it hushed up.
Are the rumours correct?
And Area51 really does have a martian spaceship.
OMG, where do you guys get or dream up these ideas???
If namespaces are used then the clash can be resolved.
There is no one "hushing" up anything. And there is nothing to "hush" up anyway.
Sheesh!!! 
4. Re: namespace bug?
- Posted by DerekParnell (admin) Apr 03, 2009
- 1010 views
- Last edited Apr 04, 2009
This is one case that triggers a warning on perfectly valid code just by adding an include:
include std/map.e ?compare(1,0)
Perfectly valid code can also contain constructs that trigger warnings. Why do you think that a warning means that you don't have valid code? A warning is NOT an error. A warning is a warning.
Yes, the code above is valid and it can trigger a warning.
You want to get rid of the warning? Sure ... try these ...
include std/map.e ?eu:compare(1,0) -- Use the predefined 'eu' namespace
without warning -- avoid all warnings include std/map.e ?compare(1,0)
without warning &=(builtin_chosen) -- avoid just the "builtin_chosen" warning. include std/map.e ?compare(1,0)
Note that adding a namespace qualifier on the include std/map.e will not avoid this warning because Euphoria still can't be certain which "compare" you are trying to reference. You have to use a namespace on the actual reference itself to disambiguate it.
5. Re: namespace bug?
- Posted by useless Apr 03, 2009
- 1053 views
- Last edited Apr 04, 2009
I just heard a rumour that a user function name which is the same name as a builtin name will clash even if namespacing is used to clarify which function is being specified. Then i heard people knew about it, and voted to allow this to continue. And people who knew about it kept it hushed up.
Are the rumours correct?
And Area51 really does have a martian spaceship.
OMG, where do you guys get or dream up these ideas???
If namespaces are used then the clash can be resolved.
There is no one "hushing" up anything. And there is nothing to "hush" up anyway.
Sheesh!!!
From a couple dev's in #euphoria.
useless
6. Re: namespace bug?
- Posted by jeremy (admin) Apr 03, 2009
- 1003 views
- Last edited Apr 04, 2009
From a couple dev's in #euphoria.
Um, no one said anything about hushing things up 
Jeremy
7. Re: namespace bug?
- Posted by jimcbrown (admin) Apr 03, 2009
- 978 views
- Last edited Apr 04, 2009
From a couple dev's in #euphoria.
Um, no one said anything about hushing things up
Jeremy
It turns out the dev's in #euphoria were even more confused. 
8. Re: namespace bug?
- Posted by useless Apr 04, 2009
- 1000 views
From a couple dev's in #euphoria.
Um, no one said anything about hushing things up
Jeremy
It turns out the dev's in #euphoria were even more confused.
Thanks for clearing this up!
useless
9. Re: namespace bug?
- Posted by DerekParnell (admin) Apr 04, 2009
- 1077 views
I just heard a rumour that a user function name which is the same name as a builtin name will clash even if namespacing is used to clarify which function is being specified. Then i heard people knew about it, and voted to allow this to continue. And people who knew about it kept it hushed up.
Are the rumours correct?
And Area51 really does have a martian spaceship.
OMG, where do you guys get or dream up these ideas???
If namespaces are used then the clash can be resolved.
There is no one "hushing" up anything. And there is nothing to "hush" up anyway.
Sheesh!!!
From a couple dev's in #euphoria.
useless
Well like most conspiracy theories, this one was false too. It seems to have been based on the usual mixture of misunderstanding and accidental misinformation.
Someone thought that this namespace thing would cause a compiler error and when they found out that it had been changed to be just a warning now, he was not aware of any discussion or reason behind the change (even though he approves of the change). No hushing up involved, just a missed message many months ago.
10. Re: namespace bug?
- Posted by bernie Apr 04, 2009
- 1019 views
I have experienced NO bugs in namespace on ver 4
In fact ver 4 has uncovered hidden bugs in MY code that ran perfectly happy on ver 3.11.
There is no reason fear using ver 4.
