Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 9.0
  • 8.0
  • rosuav/latex-markdown-renderer
  • rxnpatch/rxnpatch
  • marcus/gobject-introspection
  • rxnpatch/8.0
  • rosuav/pre-listening-ports
  • 7.8
  • nt-tools
  • 7.6
  • 7.4
  • 7.2
  • 7.0
  • rosuav/async-annotations
  • rosuav/pgsql-ssl
  • rxnpatch/rxnpatch-broken/2023-10-06T094250
  • grubba/fdlib
  • grubba/wip/sakura/8.0
  • grubba/wip/sakura/master
  • v8.0.1990
  • v8.0.1988
  • v8.0.1986
  • rxnpatch/clusters/8.0/2025-04-29T124414
  • rxnpatch/2025-04-29T124414
  • v8.0.1984
  • v8.0.1982
  • v8.0.1980
  • v8.0.1978
  • v8.0.1976
  • v8.0.1974
  • v8.0.1972
  • v8.0.1970
  • v8.0.1968
  • v8.0.1966
  • v8.0.1964
  • v8.0.1962
  • v8.0.1960
  • v8.0.1956
  • rxnpatch/clusters/8.0/2025-02-05T103156
40 results

pike

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Arne Goedeke authored
    Character ranges of strings are stored in two unsigned chars. For wide
    strings, the values between 0 and 255 represent blocks of 255 and
    (1<<24) characters, respectively.
    
    The previous code had several issues:
    
    1) After calculating the actual min/max values of the character range,
       these value were rounded up, which could lead to an overflow. The
       result was that both min and max could end up being 0. An example is
       the string (string)({ (1<<16)-1 }).
    2) The 32 bit case used blocks of 16 bit instead of 24 bit.
    f1298df3
    History
    Name Last commit Last update