On Mon, Apr 30, 2012 at 3:13 PM, Jordi Gutiérrez Hermoso <jord...@octave.org> wrote: > 2012/4/30 Michael Goffioul <michael.goffi...@gmail.com>: >> Because MSVC is not part of the officially supported compilers for octave. > > Aw, don't feel that way.
Technically, this is true. You can't compile octave with MSVC without patching the sources. > We prefer gcc, but we really don't do things > specific to any compiler, or try not to. By experience, I know that if something does not compile with GCC (like an older/newer version of GCC), octave code will be fixed. If the same happen with MSVC, it'll be "ask MS to fix their compiler". I've learned to live with it and I don't report MSVC-only compilation problems anymore. Until gcc-4.7, missing return statements was a MSVC-only problem. > After all, there are all > those __WIN32__ macros in Octave you put in, so we even make an > attempt to get it to compile on Windows. Most (all?) of these are also valid for MinGW, that's why there're still present. > Plus, this is obviously a > problem, on any compiler, so even if older gcc accepted no return > statement in non-void functions, it should be fixed. > > And this is for Octave-Forge, where they have much more lax coding > standards, so you don't even have to follow core's standards of > rigour. Did you see this problem with no return value in core? If there were any, I probably fixed them when I ported octave code to native Win32 (back in... 2007, I think), as I was already using MSVC. But to be honest, I don't think there was any such errors in core octave. Michael. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
