Octave 3.0.1 bug_report fails

[John W. Eaton]

On 26-Aug-2008, Benjamin Lindner wrote:

| >> If so, then who will take on
| >> the job of ensuring that the behavior of the separate versions of
| >> these programs are equivalent?
| > 
| > Those scripts actually change very rarely. Maintaining
| > equivalence does not seem to be a tough job. Currently,
| > when I detect a change has been made on mkoctfile,
| > I port it to my C++ version, but I think it only happened
| > once or twice. 
| 
| I agree with michael here.
| I too have an eye on either michael's .cc sources or the script versions 
| and try to update the .cc on demand.
| 
| > However, it may happen that I miss some
| > changes, so if both script and C++ version are going to
| > co-exist, it would be nice that if anybody makes a change
| > to one version, either he also port the change to the other
| > version or notifies the mailing list about the change and
| > ask for someone (for instance me) to port it.
| > 
| 
| Again agreed.
| A notification on the list would be good.
| If michael agrees, I'd also in case try to update the .cc sources, since 
|   we should use the same for msvc and mingw

OK.

What about including the C++ versions in the Octave sources and only
building them (at least for now, maybe always) on Windows systems?  Is
there any objection to doing that?

jwe