Skip to content
Snippets Groups Projects
Select Git revision
  • 251e57626bdc9738ca0b751184a080b60380e116
  • develop default protected
  • feature/gmsh-reader
  • origin/stage/bouguettaia
  • feature/kinetic-schemes
  • feature/reconstruction
  • feature/local-dt-fsi
  • feature/composite-scheme-sources
  • feature/composite-scheme-other-fluxes
  • feature/serraille
  • feature/variational-hydro
  • feature/composite-scheme
  • hyperplastic
  • feature/polynomials
  • feature/gks
  • feature/implicit-solver-o2
  • feature/coupling_module
  • feature/implicit-solver
  • feature/merge-local-dt-fsi
  • master protected
  • feature/escobar-smoother
  • v0.5.0 protected
  • v0.4.1 protected
  • v0.4.0 protected
  • v0.3.0 protected
  • v0.2.0 protected
  • v0.1.0 protected
  • Kidder
  • v0.0.4 protected
  • v0.0.3 protected
  • v0.0.2 protected
  • v0 protected
  • v0.0.1 protected
33 results

pugs

Stephane Del Pino's avatar
Stéphane Del Pino authored
Values are no more stored into AST nodes. The reason for that is that it was not
appropriate for multi-threaded evaluation of functions, since multiple
evaluations could not occur at the same time.

Now expression evaluation do not fill the node value but eventually return the
computed value.

Also, function are evaluated using a context array of values. Thus each function
calls is done in a separated context (as it should have always been).

This is a big change in the AST execution strategy. Nonetheless, it leads to a
seemingly better code, and there will be no more undefined trailing values in
the AST (for some node ASTNode::m_value would never be initialized/used).
620be0d6
History
Name Last commit Last update