Apr 16 09:15:22 xhoch3: Can I start changing the style to GNU style? Apr 16 09:18:00 okay, just tell what that means :P Apr 16 09:18:15 whitespace changes only. Apr 16 09:18:18 foo() Apr 16 09:18:19 { Apr 16 09:18:22 bar(); Apr 16 09:18:24 } Apr 16 09:18:33 Basically, that. Apr 16 09:18:40 me* Apr 16 09:19:46 actually, I used to change everything to Qt style Apr 16 09:20:19 Yeah, but if we want this to be in GNU... Apr 16 09:20:51 is there a style-guide documented? Apr 16 09:21:13 http://www.gnu.org/prep/standards/ Apr 16 09:21:44 http://www.gnu.org/prep/standards/standards.html#Formatting Apr 16 09:23:25 uh, it's exactly what I hate most, but okay Apr 16 09:23:29 It takes a while to get used to it, heh. Apr 16 09:23:37 I don't mind it now. Apr 16 09:23:49 okay Apr 16 09:23:55 how about class names? Apr 16 09:24:04 is it My_Class Apr 16 09:24:09 No preference on that. Apr 16 09:24:12 because the guide speaks of C formatting, not C++ Apr 16 09:24:15 Octave generally uses camelcaps. Apr 16 09:24:22 CamelCaps, I mean. Apr 16 09:24:56 well, classes are not C however Apr 16 09:25:35 Yeah, just use CamelCaps. Apr 16 09:26:24 mh, I really think whoever wrote this, it's really outdated Apr 16 09:26:34 and it has been outdated years before Apr 16 09:26:49 What, the GNU coding standards? Apr 16 09:26:53 They're from 1985 or so. Apr 16 09:27:05 But whatever, it doesn't matter what style you use as long as you use one. Apr 16 09:27:12 if we are strict here, Quint is not written in C, so there is no restrictions opposed on this Apr 16 09:27:17 No no no.. Apr 16 09:27:19 Look at the C++ code. Apr 16 09:27:40 Look for example at how liboctave/Sparse.h and liboctave/Sparse.cpp are formatted. Apr 16 09:28:14 Don't fight it, it's just a style guide. What editor do you use? Just configure it to use it. What's important is consistency. Apr 16 09:28:17 Er, I meant, Sparse.cc Apr 16 09:28:52 (yeah, hm, file names, don't know if that matters) Apr 16 09:29:30 * JordiGH has quit (Ping timeout: 240 seconds) Apr 16 09:29:30 * Disconnected (Remote host closed socket). **** ENDING LOGGING AT Sat Apr 16 09:29:30 2011 **** BEGIN LOGGING AT Sat Apr 16 09:29:50 2011 Apr 16 09:29:50 * Now talking on #octave Apr 16 09:29:50 * Topic for #octave is: GNU Octave discussion: http://octave.org | Octave 3.4 released: http://www.gnu.org/software/octave/NEWS-3.4.html | Also check out ##matlab | Exciting new Qt GUI: https://github.com/jacobdawid/Quint | Available functions: http://octave.sf.net/functions_by_alpha.php help us implement more! Apr 16 09:29:50 * Topic for #octave set by jgh!~jordi@octave/developer/JordiGH at Thu Apr 14 11:41:07 2011 Apr 16 09:29:51 Ugh, what was the last thing I said? Apr 16 09:30:10 CamelCaps, I mean Apr 16 09:30:39 well, I don't care what style however, but I'd like to have it consistent Apr 16 09:30:43 No no no.. Apr 16 09:30:43 Look at the C++ code. Apr 16 09:30:43 Look for example at how liboctave/Sparse.h and liboctave/Sparse.cpp are formatted. Apr 16 09:30:43 Don't fight it, it's just a style guide. What editor do you use? Just configure it to use it. What's important is consistency. Apr 16 09:30:43 Er, I meant, Sparse.cc Apr 16 09:30:43 (yeah, hm, file names, don't know if that matters) Apr 16 09:31:38 well, it won't be consistent Apr 16 09:31:44 Why not? Apr 16 09:31:45 since Qt is not formatted this way Apr 16 09:31:53 it will be a heavy mix of both Apr 16 09:31:57 Is Qt C++? Apr 16 09:32:00 yes Apr 16 09:32:07 Then why not format it like C++? Apr 16 09:32:28 Qt is formatted like C++ Apr 16 09:32:38 Good, then format it like our C++. Apr 16 09:33:07 like it should be Apr 16 09:33:09 well, anyways, we can't change that Apr 16 09:33:16 We can't change what? The formatting? Apr 16 09:33:19 I mean the Qt classes Apr 16 09:33:21 I'll do it. Apr 16 09:33:22 QString Apr 16 09:33:29 What's wrong with that? Apr 16 09:33:31 QFileDialog Apr 16 09:33:40 I don't think you're listening... :-( Apr 16 09:33:42 CamelCaps are fine. Apr 16 09:33:45 it's not Q_File_Dialog Apr 16 09:33:47 Look at liboctave/Sparse.h Apr 16 09:34:16 I'm just talking about the whitespace things. Apr 16 09:34:16 okay, wait a second Apr 16 09:37:09 class SparseQR_rep Apr 16 09:37:20 that's C formatting Apr 16 09:37:25 =) Apr 16 09:37:32 There isn't anything C or C++ about camelcaps vs underscores. Apr 16 09:37:47 SparseQRRep looks kinda ugly, if you ask me. Apr 16 09:37:56 ,tr en pt-br larts Apr 16 09:37:58 I think tr is use ,t8 Apr 16 09:38:12 ,tr en pt larts Apr 16 09:38:17 tr is use ,t8 Apr 16 09:38:25 are you reformatting it automatically? Apr 16 09:38:47 do you have a tool? Apr 16 09:39:26 Yes, Emacs. Apr 16 09:39:38 I'm just gonna do whitespace changes. Apr 16 09:39:57 Also, the C++ stdlib prefers underscores, for the record. Apr 16 09:40:02 But of course, Qt hates the stdlib. Apr 16 09:40:13 no, it loves Java-Style Apr 16 09:40:28 To be fair, the stdlib really sucked when Qt started, which is why Qt reimplemented large chunks of it. Apr 16 09:41:41 I hope the GNU guys will update their guidelines one day Apr 16 09:42:02 until then I'd say we have no choice ;) Apr 16 09:42:10 There isn't anything to update. It's just a style. You want Picasso to update his paintings? Apr 16 09:42:34 well, I am not Picasso Apr 16 09:42:56 but if I were doing my own paintings, they'd be different for sure ;) Apr 16 09:43:09 okay, go for it Apr 16 09:43:56 I will pull your changes then Apr 16 09:45:24 in the meantime I'll see whether I can change the standard code formatting of QtCreator