warnings which don't help user to undesrtand where the problem is

[Steven Verstoep]

>
> I have downloaded octave 3.0.3 but that only makes things worse.
>
> -*- The bug I had with fscanf is gone. I read on the internet that it 
> was a problem with 2.1.52 (and later)
>
> -*- opening octave from the command line still loads octave 2.1.53
>
> -*- the statement if(charc == '\n') is no longer true if charc is 
> indeed a newline (see code below, \n is now read as 2 characters)
>
> -*- I now get warnings on any string definition like:
>

Followup to my own mail:

I encountered that even functions like plot produced screens full of 
warnings.

I then restarted octave and all the bugs were gone.

I don't know what is wrong. Maybe I still used some old settings file.

I use a PowerPC Mac 10.3.9 by the way.

regards.


Steven Verstoep