Octave 3.0.1 bug_report fails

[Thomas Weber]

On 11/07/08 22:26 +0200, Michael Goffioul wrote:
> The nice thing about the script version is that it's rather easy to
> maintain, does not require compilation, can make use of all
> standard UNIX tools (sed, grep...) and is UNIX-cross-platform.

I'll add that you can simply read the code in order to find a variable you
want to query (i.e., you know what type of path you want and just look for a
corresponding variable name).
 
> The problem is that they're unusable under Windows
> (even on MinGW-compiled octave). The 3 C++ version I wrote
> however are quite different:
> 
> - mkoctfile.cc is a real one-to-one translation of the script
> version; this one was mandatory to have under Windows
> in order to compile octave-forge packages for instance
> 
> - octave-config.cc is there for "symmetry", but I actually
> never used it

mkoctfile and octave-config seem to have quite some overlap. How about
merging them into one file, say mkoctfile?


> - octave-bug.cc takes a radically different approach than
> the script version; this one is really Windows specific,
> although it could also include a one-to-one translation
> of the script (stream editor + mail)

Is octave-bug really used much these days? I'm under the impression that most
people simply send a mail to the list using their favorite MUA. 

	Thomas