whats_new_24

Changes and Additions to CppAD During 2024

mm-dd

01-16

fix dll linking of jit code by changing cppad_c_compiler_path to cppad_c_compiler_cmd (spaces in the path were making commands fail).

01-12

  1. There were some problems using the cmake C compiler for the examples and tests of jit compilation, so that has been backed out for now.

  2. There was a mistake in detecting if size_t is the same as cppad_tape_addr_type. This could cause a compile error in op_hash_table.hpp and has been fixed.

01-11

Use the cppad_c_compiler_path detected by cmake to run the C compiler for the Clang and GNU cases; see the create_dll_lib` defaults for compile and link .

01-10

  1. Fix some problems with the install on 32 bit systems. To be specific, the thread_alloc memory allocator was not properly aligning doubles.

  2. Suppress the test of the svec_setvec class. (The class has a bug and is not currently being used.)

01-08

On some systems unsigned int and size_t are the same type and this would cause a compile error in vector.hpp and vector_bool.hpp . This has been fixed.

01-07

The forward_two Syntax was corrected. To be specific, Forward (1, x2 ) was changed to Forward (2, x2 ) . In addition, some other minor improvements were made to the forward_two documentation page.

01-03

  1. The change on 12-24 2023, when cppad_debug_and_release was implemented, was not done properly and might cause a mistaken assertion. This has been fixed.

  2. Each file_name in the latest documentation was moved (this is important if you have links to previous web pages):

    Old Location

    https://cppad.readthedocs.io/file_name

    New Location

    https://cppad.readthedocs.io/latest/file_name

01-02

  1. The compare_change.cpp example/test would sometimes fail when cppad_debug_which was debug_even or debug_odd (because it was compiled for debugging and including a release version of a utility). This has been fixed by making this example/test a separate program.

  2. The vectorBool constructor would generate a warning when called with an int for the size of the vector (on some compilers). This has been fixed.