propeller-load bug or feature? no line-feed character
DavidZemon
Posts: 2,973
I would certainly classify this as a bug.... I hope it wasn't the intended execution...
PropGCC's "propeller-load -t" sends only a carriage return upon pressing enter - no line feed. I understand that the Simple library and presumably C standard library in PropGCC are okay with this... but that can't possibly be normal can it? What about when you connect to the board from any other terminal and you are using a buffered UART? Any other terminal will send perhaps just a line feed or a line feed and carriage return and - if using buffered UART - then you find yourself with a dangling line feed character in the buffer. Why don't the Prop libraries look only for line feed and propeller-load send only line-feed. Wouldn't that be more normal?
PropGCC's "propeller-load -t" sends only a carriage return upon pressing enter - no line feed. I understand that the Simple library and presumably C standard library in PropGCC are okay with this... but that can't possibly be normal can it? What about when you connect to the board from any other terminal and you are using a buffered UART? Any other terminal will send perhaps just a line feed or a line feed and carriage return and - if using buffered UART - then you find yourself with a dangling line feed character in the buffer. Why don't the Prop libraries look only for line feed and propeller-load send only line-feed. Wouldn't that be more normal?
Comments
if everybody else has noticed it and NOT complained, then its maybe NOT a bug.
I use a terminal program that can be configured, each thing tends to be different from the last.
Do you ever use C/C++ and the default serial tools (I'm pretty sure all of the standard tools use buffered UARTs)? If so, how do you have your terminal program configured?
No, SimpleIDE doesn't use it.
I'm sure David Betz uses "propeller-load -t" ....
That has to be the most unexpected thing I have ever heard to be "normal". Certainly good to know though.
I [essentialy] copied/pasted the code from Simple's getStr. When I first did that a few weeks ago I was thinking "this is a WEIRD way to handle CR/LF" but didn't look into it. Now I understand.