Jaroslav Hajek wrote: > That's really weird, because looking at the code, it should fail > AFAIK. Array<T> should be always instantiated using the > INSTANTIATE_ARRAY macro (which overrides > Array<T>::instantiation_guard). This was done because implicit > instantiations of Array<T> should basically never happen, so that we > want to guard against them. > > Replacing the template statements by INSTANTIATE_ARRAY should fix the > problem. I'll patch it later if you won't do it sooner. > > regards > > Ok I undetstand my 0.7.10 was built from the SVN with a patch form the 13 June.. The last release of octave-forge was 8 June and so the difference is the instantiation.. So this seems to already be patched.. The next release of octave-forge will fix this issue.
D. -- David Bateman dbate...@dbateman.org 35 rue Gambetta +33 1 46 04 02 18 (Home) 92100 Boulogne-Billancourt FRANCE +33 6 72 01 06 33 (Mob) ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
