I am testing this simple code with a namespace, and I am getting "sketch_nov03a:8: error: 'namespaceTest' does not name a type" error.
This works perfectly fine in any older version of the IDE . How to enable Arduino IDE 1.6.6 to compile namespaces? I need them for my project.
namespace Test
{
}
void setup() {
// put your setup code here, to run once:
}
void loop() {
// put your main code here, to run repeatedly:
}
Delta_G:
Did you copy and paste that or just type it back in to the post?The reason I ask is that in your posted code there is a space between namespace and Test like there should be. But in the error message there is no space, it's all jammed into one word.
yes, the code is pasted from the original sketch. No matter how many spaces I add the error reports it like : 'namespaceTest' 
.
I am installing a clean VM to test there. Did the install on my main system, and want to make sure this is not due to some old version or something...
This is a 1.6.6 specific issue. It works fine with all other versions .
I need to have some of the code of the sketch in namespaces, as the code is generated by Visuino and in order to avoid name conflicts I have to organize it in namespaces.
Delta_G:
The simplest answer would be to back off a version. There's no rule that says you always have to use the latest release. I usually don't just for this reason, unknown issues.
The problem is that I need to support the latest version with Visuino. What to do with the users that try to use it with 1.6.6 ? Tell them all to switch to the older version? This is a very simple code, and there should not be a problem compiling it . It's not like it is something really complex, it's just a namespace declaration...
Delta_G:
It is perfectly reasonable to tell a library user what version your code works with. 1.6.6 won't be the last. What if you get this all working and everything is good and then 1.7 comes out and they rename digitalRead or something?
It's not a library users. It is the Visuino users - https://www.visuino.com aver 6000 of them already :-(, and those are just in the community, I am scared of what will happen in few days...
OP reported this issue to the tracker: Arduino IDE 1.6.6 does not compile code with namespaces · Issue #4075 · arduino/Arduino · GitHub
Delta_G:
You've still got the same issue. Even if you get it working with 1.6.6, there's no guarantee that it works with the next version.
So, I guess your attitude is just ignore bugs because they don't get fixed...Huh?
Some of us don't have the luxury of using a year plus old IDE, we have newer items that rely newer coding.
Delta_G:
No, not at all. My attitude is to use stable code. The latest release of anything open source rarely meets that requirement. I tend to think of the latest as the "experimental version" that we hope works and the one before it as the "one that's known".
My problem is that I provide IDE to support very much any Arduino compatible platform with very much any tool-chain, but the end users may have different Arduino IDE already installed. My IDE has to work with whatever they already have . It is a big problem when the current official Arduino IDE is so broken
Delta_G:
And even if they fix this in 1.6.7, you're still going to have to tell people it doesn't work with 1.6.6 because that has been released so it's not going to change.
It is not problem when the current official version works, as they usually always check that. so when they fix in 1.6.7 and make it official, this will not be a problem. Until then, I am in big trouble
Delta_G:
I'm sure the brightest minds in open source programming are on the case and you'll get a fix in a few weeks / months / years.
It's already been fixed, took less than 6 hours from the time it was reported. I'm guessing there will be a 1.6.6r2 released as with 1.6.5 so that it won't have to wait for 1.6.7 to be released. Until then people can use the current hourly build which right now is almost the same as 1.6.6 so not much extra concerns about being beta software.
Edit: 12 hours
pert:
It's already been fixed, took less than 6 hours from the time it was reported. I'm guessing there will be a 1.6.6r2 released as with 1.6.5 so that it won't have to wait for 1.6.7 to be released. Until then people can use the current hourly build which right now is almost the same as 1.6.6 so not much extra concerns about being beta software.Edit: 12 hours
Thank you! Can't wait for the 1.6.6r2 to be out with the fix 
Hope it is soon!
I have released Visuino Beta 73, and it includes a workaround for the remaining bug in the 1.6.7 hourly builds.
I hope the remaining bug will also be fixed. I have offered to Federico Fissore to have remote access to my test VMs so he can investigate it, and hopefully it will be fixed soon too
mitov:
I hope the remaining bug will also be fixed.
Just curious, what's the remaining bug?
pert:
Just curious, what's the remaining bug?
I'd advise in the future to test Visuino against the hourly build so you can report these issues before the new version is released. The difficulty with this is that they don't seem to give any advance warning before the release. On GitHub you can see the progress indicator to the next milestone but then they release before the milestone was reached.
pert:
I'd advise in the future to test Visuino against the hourly build so you can report these issues before the new version is released.
Thank you! I think I have learned an important lesson, and will try my best to do this, regardless of the overload here 