[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #56419] Implementation of newline
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #56419] Implementation of newline |
Date: |
Thu, 30 May 2019 13:16:13 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36 |
Update of bug #56419 (project octave):
Severity: 3 - Normal => 1 - Wish
Item Group: Matlab Compatibility => Feature Request
Status: None => Patch Reviewed
_______________________________________________________
Follow-up Comment #1:
Thank you for working on this. This is a good idea and a nice and simple built
in implementation.
A few comments or suggestions:
* The doc string should use the Texinfo '@xbackslashchar' macro instead of a
literal backslash, and the '@qcode' macro instead of '@code'
* What is the relevance of the see also references to sprintf and char?
Wouldn't functions like strcat, strjoin, or strsplit be more relevant?
* Is it better to report nargout > 1 with the usage message or with the
default error handling? IOW, which of the following error messages is more
user friendly?
>> [a, b] = newline ()
error: Invalid call to newline. Correct usage is:
-- newline ()
>> [a, b] = newline ()
a =
error: element number 2 undefined in return list
IMHO the second is clearer to the user and more consistent with other
functions that are called with too many return values requested.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?56419>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/