lua/lstring.h, branch v5.5.1A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.5.12025-10-14T16:50:24+00:00Details2025-10-14T16:50:24+00:00Roberto Iroberto@inf.puc-rio.br2025-10-14T16:50:24+00:00urn:sha1:9c66903cc55388006a833f0f3911ea81fa86edea
- Functions luaK_goiffalse, luaS_hash made private.
- Removed unused macro log2maxs.
Short strings can be external, too2025-07-15T17:40:27+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-07-15T17:40:27+00:00urn:sha1:60b6599e8322dd93e3b33c9496ff035a1c45552f
That complicates a little object equality (and therefore table access
for long strings), but the old behavior was somewhat weird. (Short
strings, a concept otherwise absent from the manual, could not be
external.)
Scanner doesn't need to anchor reserved words2024-12-30T19:53:51+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-12-30T19:53:51+00:00urn:sha1:5894ca7b95d7fb05f1e93ee77e849a8d816d1c6dAdded gcc option '-Wconversion'2024-07-27T16:32:59+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-07-27T16:32:59+00:00urn:sha1:0acd55898d0aaae8dbc14c8a1bc1e3bdffc8701b
No warnings for standard numerical types. Still pending alternative
numerical types.
Cleaning of llimits.h2024-06-20T16:43:33+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-06-20T16:43:33+00:00urn:sha1:55ac40f859ad8e28fe71a8801d49f4a4140e8aa3
Several definitions that don't need to be "global" (that is, that
concerns only specific parts of the code) moved out of llimits.h,
to more appropriate places.
Some 'unsigned int' changed to 'unsigned'2024-03-22T17:06:11+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-03-22T17:06:11+00:00urn:sha1:9fa63a62682c1353eeabd4575152941fa6f3e70f
'unsigned int' is too long sometimes. (We already write 'long' instead
of 'long int'...)
External strings2023-11-09T20:05:42+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-11-09T20:05:42+00:00urn:sha1:024f9064f1b43758eb36aba52547edc0312bf4ba
Strings can use external buffers to store their contents.
Towards external strings2023-11-08T16:24:38+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-11-08T16:24:38+00:00urn:sha1:7f4906f565ab9f8b1125107a3abae3d759f3ecf2
Long strings have a pointer to string contents.
Hash always use all characters in a long string2020-10-12T15:29:09+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-10-12T13:02:37+00:00urn:sha1:9a89fb1c9dfeda4640780111f9e9437f08cfad88
Hashes for long strings are computed only when they are used as keys
in a table, not a too common case. And, in that case, it is to easy to
force collisions changing only the characters which are not part of the
hash.
Cleaner definition for 'TString'2020-05-19T15:42:20+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-05-19T15:42:20+00:00urn:sha1:9514abc2da3525ef4314a8fcf70982ad07319e51
Use a variable-sized array to store string contents at the end of a
structure 'TString', instead of raw memory.