scintilla-mirror/lexers/LexHex.cxx, branch rel-5-3-3 Git mirror of the Scintilla editor component. Referenced by the SciTECO repository. Remove Lexilla files from Scintilla 2021-01-29T09:51:34+00:00 Neil nyamatongwe@gmail.com 2021-01-29T09:51:34+00:00 54341053b273c905afa7503d8dadcc4c46a0d2d3 






The Scintilla namespace is always active for internal symbols and for the lexer
2017-09-10T23:05:35+00:00

Neil
nyamatongwe@gmail.com

2017-09-10T23:05:35+00:00

313a81f7f8419b3c1ac6ac57ea7719c7b8aa28cf

interfaces ILexer4 and IDocument.





interfaces ILexer4 and IDocument.







Update types for Unix LP64 after changes to Sci_Position/Sci_PositionU.
2017-07-17T05:18:31+00:00

Neil Hodgson
nyamatongwe@gmail.com

2017-07-17T05:18:31+00:00

7f6f9643d38f799155a76c108c8273f5cb2136ca












Use Sci_Position / Sci_PositionU for variables in lexers that represent
2015-07-30T04:35:17+00:00

Joe Mueller
unknown

2015-07-30T04:35:17+00:00

58471e908a3b74b27379bb19a13d62cd8d4476b0

positions and line numbers and may be widened to 64-bits in a future release.





positions and line numbers and may be widened to 64-bits in a future release.







Use Sci_PositionU/Sci_Position for arguments to functional lexers, folders, and
2015-07-25T01:25:56+00:00

Neil
nyamatongwe@gmail.com

2015-07-25T01:25:56+00:00

c30768f1167cfe590e0b6a12c4a986e82a210cc3

comment recognizers to allow for future implementation of 64-bit positions.





comment recognizers to allow for future implementation of 64-bit positions.







LexHex S-Record: use the required data field size for some highlighting
2015-01-12T23:59:18+00:00

Markus Heidelberg
markus.heidelberg@web.de

2015-01-12T23:59:18+00:00

4bb00a25f379684744b3e28cbf435f21650efc8d

Equal to how it is already implemeted for the Intel HEX lexer.

Specific record types do not use a data field, the checksum field
directly follows the address field then.
In these cases now the byte count field is also marked as wrong if its
content is not what is to be expected for this record type. Also the
checksum field is now fixed after the address field instead of allowing
data field in between if the byte count is too big.

Also simplify this code path for IHex to be equal to the Srec code.





Equal to how it is already implemeted for the Intel HEX lexer.

Specific record types do not use a data field, the checksum field
directly follows the address field then.
In these cases now the byte count field is also marked as wrong if its
content is not what is to be expected for this record type. Also the
checksum field is now fixed after the address field instead of allowing
data field in between if the byte count is too big.

Also simplify this code path for IHex to be equal to the Srec code.







LexHex: use SCE_HEX_RECTYPE_UNKNOWN also for Srec and IHex
2015-01-12T23:58:30+00:00

Markus Heidelberg
markus.heidelberg@web.de

2015-01-12T23:58:30+00:00

02927e5c3be78e98fa3e2beb965248f688fb8e6c












LexHex: add a default case for handling faulty states to all lexers
2015-01-10T22:04:35+00:00

Markus Heidelberg
markus.heidelberg@web.de

2015-01-10T22:04:35+00:00

88504b1be93afb6be89b1c2948453a4581d3d0eb

If the state variable is set to a state not used in this lexer, an
endless loop would occur because Forward() is never invoked then.





If the state variable is set to a state not used in this lexer, an
endless loop would occur because Forward() is never invoked then.







LexHex: add a new state for garbage data after the record
2015-01-10T22:04:00+00:00

Markus Heidelberg
markus.heidelberg@web.de

2015-01-10T22:04:00+00:00

683c68c04540c42b0b22de78da9c046b98ad50e2

IHex and Srec just set to the DEFAULT state before, TEHex used the
SCE_HEX_DATA_UNKNOWN state for garbage data, which is not the actual intention
for this state.





IHex and Srec just set to the DEFAULT state before, TEHex used the
SCE_HEX_DATA_UNKNOWN state for garbage data, which is not the actual intention
for this state.







LexHex Tektronix: use more address field types, not just data address
2015-01-10T22:03:25+00:00

Markus Heidelberg
markus.heidelberg@web.de

2015-01-10T22:03:25+00:00

52156dcd3465f5db9734b0e8ca8d726eae60c9f2

Also use the new function for checking whether the record type is
unknown.





Also use the new function for checking whether the record type is
unknown.