[Octave-bug-tracker] [bug #47258] exit() causes empty line at stdout

[Carnë Draug]

Follow-up Comment #4, bug #47258 (project octave):

> Please don't misunderstand me, I like rearranging deck chairs on sinking
ships as much as anyone, but why this particular chair?

Ah! I have never heard that expression before.  Anyway, I wouldn't compare
Octave to a sinking ship. Also, I report a lot of very minor bugs just so
they are reported somewhere.  I'm not requesting others to fix it for me.
It gives me a place to come to when I find time to do it myself, or a
starting point for someone else that may have the same itch.

> Sorry if that sounds bad, but what real problems does this cause?

I guess I am one of those odd people who write Octave programs instead of
only using the interactive session.

One of the things I have been doing a lot lately is finding centre of objects
in images.  My programs then write the coordinates of those objects to stdout
which I redirect into a file (I use a build system for my analysis, where
data is the source, results are the target, and I build the results with
my programs).

The simplest analysis of all is counting the number of objects identified.
These are just the number of lines which is trivial in the shel with wc. 
This
all worked fine for a long time but now failed once I added an exit().  Of
course, this is a very minor thing and I just fixed my own code to avoid
exit() altogether.

Still, this is wrong behaviour, Octave should only be printing newlines
if the program tells it to.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47258>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/