Skip to content
Snippets Groups Projects
  1. May 01, 2019
    • Mark OLESEN's avatar
      ENH: ensure that content changes in coded objects are noticed (#1293) · f50d23a9
      Mark OLESEN authored
      - for codedFunctionObject and CodedSource the main code snippets
        were not included in the SHA1 calculation, which meant that many
        changes would not be noticed and no new library would be compiled.
      
        As a workaround, a dummy 'code' entry could be used solely for the
        purposes of generating a SHA1, but this is easily forgotten.
      
        We now allow tracking of the dynamicCodeContext for the coded
        objects and append to the SHA1 hasher with specific entries.
        This should solve the previous misbehaviour.
      
        We additionally add information about the ordering of the code
        sections. Suppose we have a coded function object (all code
        segments are optional) with the following:
      
            codeExecute "";
            codeWrite   #{ Info<< "Called\n"; #};
      
        which we subsequently change to this:
      
            codeExecute #{ Info<< "Called\n"; #};
            codeWrite   "";
      
        If the code strings are simply concatenated together, the SHA1 hashes
        will be identical. We thus 'salt' with their semantic locations,
        choosing tags that are unlikely to occur within the code strings
        themselves.
      
      - simplify the coded templates with constexpr for the SHA1sum
        information.
      
      - Correct the CodedSource to use 'codeConstrain' instead of
        'codeSetValue' for consistency with the underlying functions.
      f50d23a9
  2. May 06, 2019
  3. May 03, 2019
  4. May 02, 2019
  5. May 01, 2019
  6. Apr 30, 2019
  7. Apr 29, 2019
  8. Apr 28, 2019
  9. Apr 26, 2019
  10. Apr 29, 2019
  11. Apr 26, 2019
  12. Apr 29, 2019
  13. Apr 26, 2019
  14. Apr 25, 2019