comparison NEWS @ 21075:5ed379c8decd

Add new function evalc to core. * NEWS: Announce new function. * eval.txi: Add DOCSTRING to manual. * pager.cc (Fdiary): Add seealso link to evalc. * __unimplemented__.m: Remove evalc from list of unimplemented fcns. * oct-parse.in.yy (Fevalc): New function with BIST tests. * oct-parse.in.yy (Feval): Add seealso link to evalc.
author Oliver Heimlich <oheim@posteo.de>
date Fri, 15 Jan 2016 09:19:46 -0800
parents f7e64e1baa08
children b433f9990452
comparison
equal deleted inserted replaced
21074:9ff2ae6cd5b0 21075:5ed379c8decd
59 to return a second output with the total number of function evaluations. 59 to return a second output with the total number of function evaluations.
60 60
61 ** Other new functions added in 4.2: 61 ** Other new functions added in 4.2:
62 62
63 deg2rad 63 deg2rad
64 evalc
64 hash 65 hash
65 im2double 66 im2double
66 psi 67 psi
67 odeset 68 odeset
68 odeget 69 odeget
94 isequalwithequalnans javamethods 95 isequalwithequalnans javamethods
95 java_convert_matrix re_read_readline_init_file 96 java_convert_matrix re_read_readline_init_file
96 java_debug read_readline_init_file 97 java_debug read_readline_init_file
97 java_invoke saving_history 98 java_invoke saving_history
98 99
99 ** The global error_state variable in Octave's C++ API has been 100 ** The global error_state variable in Octave's C++ API has been deprecated
100 deprecated and will be removed in a future version. Now the error 101 and will be removed in a future version. Now the error and print_usage
101 and print_usage functions throw an exception 102 functions throw an exception (octave_execution_exception) after displaying
102 (octave_execution_exception) after displaying the error message. 103 the error message. This makes the error and print_usage functions in C++
103 This makes the error and print_usage functions in C++ work more like 104 work more like the corresponding functions in the scripting language.
104 the corresponding functions in the scripting language.
105 105
106 ** The default error handlers in liboctave have been updated to use 106 ** The default error handlers in liboctave have been updated to use
107 exceptions. After displaying an error message they no longer return 107 exceptions. After displaying an error message they no longer return
108 control to the calling program. The error handler function can be 108 control to the calling program. The error handler function can be
109 customized through the global variables "current_liboctave_error_handler" 109 customized through the global variables "current_liboctave_error_handler"
110 and "current_liboctave_error_with_id_handler". If a programmer has 110 and "current_liboctave_error_with_id_handler". If a programmer has
111 installed their own custom error handling routines when directly linking 111 installed their own custom error handling routines when directly linking
112 with liboctave then these must be updated to throw an exception and 112 with liboctave then these must be updated to throw an exception and not
113 not return to the calling program. 113 return to the calling program.
114 114
115 ** New configure option, --enable-address-sanitizer-flags, to build 115 ** New configure option, --enable-address-sanitizer-flags, to build Octave
116 Octave with memory allocator checks (similar to those provided by 116 with memory allocator checks (similar to those in valgrind) built in.
117 valgrind) built in.
118 117
119 Summary of important user-visible changes for version 4.0: 118 Summary of important user-visible changes for version 4.0:
120 --------------------------------------------------------- 119 ---------------------------------------------------------
121 120
122 ** A graphical user interface is now the default when running Octave 121 ** A graphical user interface is now the default when running Octave