+
Point of view
All features
class JSON_PARSE_CONTEXT
Summary
top
Direct parents
Insert list: LOGGING
Class invariant
top
Overview
top
line: INTEGER_32
writable attribute
{JSON_PARSER}
top
column: INTEGER_32
writable attribute
{JSON_PARSER}
top
item: CHARACTER
effective function
{JSON_PARSER}
top
require
is_valid: BOOLEAN
effective function
{JSON_PARSER}
top
next
effective procedure
{JSON_PARSER}
top
require
skip_blanks
effective procedure
{JSON_PARSER}
top
ensure
skip (word: STRING): BOOLEAN
effective function
{JSON_PARSER}
top
require
  • not word.is_empty
error (str: ABSTRACT_STRING)
effective procedure
{JSON_PARSER}
top
require
  • str /= Void
debug_position: ABSTRACT_STRING
effective function
{JSON_PARSER}
top
ensure
  • Result /= Void
writable attribute
{}
top
index: INTEGER_32
writable attribute
{}
top
writable attribute
{}
top
effective procedure
{}
top
require
  • a_data.is_connected
ensure
item_or_invalid: ABSTRACT_STRING
effective function
{}
top
delay_fix_position: BOOLEAN
writable attribute
{}
top
fix_position
effective procedure
{}
top
_inline_agent6: ABSTRACT_STRING
frozen
effective function
{}
top
log: LOGGER
effective function
{}
top
There is one logger per concrete type; for performance reasons it is cached in each instance.
ensure
  • Result /= Void
log_memory__0_: LOGGER
writable attribute
{}
top
The cached logger.
The ugly name is intentional. Don't use directly.