|
| From: | Rik |
| Subject: | [Octave-bug-tracker] [bug #42936] set(gca, 'xtick', []) fails to remove ticks [PATCH] |
| Date: | Fri, 08 Aug 2014 16:53:45 +0000 |
| User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 |
Update of bug #42936 (project octave):
Status: Need Info => Fixed
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #5:
I modified your patch to use the Octave coding conventions and checked it in
here (http://hg.savannah.gnu.org/hgweb/octave/rev/1ad621d894ba).
The list of coding conventions is in the pdf manual in Appendix D. But what I
did was simple
1) Use space between function name and opening parenthesis. We cuddle the
parenthesis when the operation is indexing and this serves as a nice visual
clue.
2) Use '##' to start stand-alone comments.
3) Use enclosing parentheses around test conditions in if statements as in the
C language.
4) Changed isequal (XXX, []) to just isempty (XXX)
Thanks for the patch and I'm closing the report now.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?42936>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |