Martin Helm wrote: > Am Donnerstag, 22. Juli 2010 00:58:46 schrieb Charles Yee: <snip> >> bool)’: __java__.cc:223: error: ‘getcwd’ is not a member of ‘octave_env’ > > I compiled the java package succesfully with octave 3.3.52 (should work the > same with 3.3.51) by changing the __java__.cc code. > > getcwd is no longer part of the octave api and is replaced by > get_current_directory. So edit the __java__.cc file and replace every > occurence of getcwd with get_current_directory.
Is there a way to make __java__.cc check the running octave version and invoke the appropriate call? (#ifdef or so? - I'm not very proficient in c++, sorry) I think this can be very useful as the java package is used in octave 3.2.4 and earlier but should also work in 3.3.51 and up. Maintaining two java pkg versions or dropping/neglecting octave versions seems not the right thing to me. On a related note, Martin Hepperle made a "java-1.2.8" pkg a while ago. I'm helping him to turn it into patches (or separate files) suitable for committing into the svn tree. He made a number of IMO very useful additions and methods, e.g., javarmpath(), dialog boxes, wrappers for better ML compatibility, etc. In addition, the split() call in javaclasspath.m should be replaced by strsplit() (which may break compatibility with older octave versions that -however- IMO are severely outdated at this point) and there are one or two other (minor) issues. When we're ready testing the "1.2.8" package, shall I send the changed and added files for reviewing to the list or just to you, Michael? There's perhaps some interference to be expected in a later stage w.r.t. to the getcwd/get_current_directory call. Thanks, Philip ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
