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. We prefer gcc, but we really don't do things specific to any compiler, or try not to. 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. 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? - Jordi G. H. ------------------------------------------------------------------------------ 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
