Purpose of record Token's x, y, and i fields?

[parke]

Question # 2:

I'm guessing that: Teal's lexer stores newline information in a Token's y field. (And that the lexer does not store or pass newline information via any other mechanism.)

This would mean that the pretty-printer that turns the ast back into a string injects newlines every time it detects a new y (i.e. a new line number)? Is this correct?

Question # 1 (probably answered below):

What is stored in Token's x, y, and i fields?

local record Token
   x: integer
   y: integer
   i: integer
   tk: string
   kind: TokenKind
end

[parke]

Are the comments I have added to t.lex() correct?

   function tl.lex(input: string): {Token}, {Token}
      local tokens: {Token} = {}

      local state: LexState = "any"
      local fwd = true
      local y = 1   --  the current source code line number?
      local x = 0   --  the current source code column number?
      local i = 0   --  the current source code byte offset from beginning of file?
      local lc_open_lvl = 0
      local lc_close_lvl = 0
      local ls_open_lvl = 0
      local ls_close_lvl = 0
      local errs: {Token} = {}
      local nt = 0

      local tx: integer   --  the column the current token begins on?
      local ty: integer   --  the line the current token begins on?
      local ti: integer   --  the byte offset (from the beginning of the file) of the first character of the current token?
      local in_token = false

[hishamhm]

yes, those are correct!