Skip to content
Snippets Groups Projects
Select Git revision
  • 4a03910c548cc3e3cc24b1b0c64ca1b2377a4acc
  • master default protected
  • nightly_master
  • online_much_readconf_cleanup protected
  • online_mvd_readconf_cleanup protected
  • jul25_patches
  • cleanup_rich_v25a
  • jul24_patches
  • nov23_patches
  • DC_2404
  • nighly_master
  • DC_Jan24
  • DC_Nov23
  • DC_Oct23
  • feb23_patches
  • L1Algo-dev9
  • dec21_patches protected
  • apr21_patches protected
  • dev_2025_47
  • RC2_jul25
  • dev_2025_46
  • dev_2025_45
  • dev_2025_44
  • dev_2025_43
  • dev_2025_42
  • dev_2025_41
  • dev_2025_40
  • dev_2025_39
  • dev_2025_38
  • dev_2025_37
  • dev_2025_36
  • dev_2025_35
  • dev_2025_34
  • dev_2025_33
  • dev_2025_32
  • dev_2025_31
  • dev_2025_30
  • RC_jul25
38 results

check-file-ending.sh

Blame
  • Florian Uhlig's avatar
    Administrator authored
    According to the Posix standard a line of a text is defined as follows:
    
    3.206 Line
    A sequence of zero or more non- <newline> characters plus a terminating
    <newline> character.
    
    The test checks if this is valid for all newly added or changed text files.
    
    I stumbeled over the issue when adding a new header file the list of header
    files used to generate a ROOT dictionary.
    The previous last file of the list did not have a proper file ending and
    attaching the new header file results in a ROOT dictionary source code with
    the following line
    
    '#endif#ifdef'
    
    which could be properly parsed and compiled by the compiler but results in an
    error at run time when loading the library.
    
    To avoid such problems in future the test was added.
    d3b39189
    History
    check-file-ending.sh 1.34 KiB