Got this rather bizarre error today- I was trying to make an error message stand out by adding "!!!" to the end of it, and when I uploaded it to the board the statusbar got to about 90% and never finished. I tracked down the problem to the "!!!" and was able to replicate it with this small program, which also refuses to load:
No a well documented Bug is called a Feature, That particular Feature prevents you from making a minor grammatical error and thus impressing your best mates with your clear lack of erudition.
It's very well documented in the sense that it comes up in the forum from time to time. The problem is that search engines like Google ignore punctuation marks. So how does one search for and find reference to this issue?
AWOL:
But, apart from ellipsis, I can't think of a good reason for three consecutive punctuation marks.
People use it for extra expression (e.g. FIRE!!!).
This bug only occurs on the Arduino Mega.
Does anyone know exactly what causes the error? Everyone just says it is a well documented bug.
AWOL:
Why would you ever need more than one exclamation mark?
Well, the OP says:
dlworrell:
I was trying to make an error message stand out by adding "!!!" to the end of it...
I do this sort of thing all the time (though I add annotations to the beginning of log lines, not the end.) I use ! usually because I might be searching logs with a text editor that treats things like * special, and I want something quick and dirty that stands out.
This bug violates the principle of least surprise, which is why we are all having this conversation -- someone got surprised again, and then further surprised that others were surprised that he or she didn't know about the surprise.
I've heard !!! starts the usb to serial chip's debugger.
This could go in the post at the top of the forum. Or maybe have a separate one for "Known bugs." Or have it point to the list of known bugs on the google code page.
It's the 2560 bootloader, which has a "monitor mode" entered with the !!! Sequence.
Not the serial chip code. UNO doesn't have such a monitor and does not have a version of this bug.