Update of ”Parsing in detail”
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview

Artifact ID: cc858b835f18453ce89ae38058cd3466985c4c7c
Page Name:Parsing in detail
Date: 2016-06-25 19:12:52
Original User: dgp
Mimetype:text/x-markdown
Parent: 43fa8c63215b00906ab420c571a9ec2d2060a1ed (diff)
Next 6007c401e0396a9cc47b38e73b005b2dc867e046
Content

The first phase of any Tcl script evaluation is applying Tcl's parsing rules for breaking the script into its component parts. Note that the interp is not an input into the parsing operation. No interp state has any controlling effect on the way a Tcl script is parsed. The same string is always parsed into the same tokens.

Inputs

  • Script: a Unicode codepoint sequence of known length.

Outputs

  • Code: integer value
  • Result:
  • Parse tree that partitions the input script into substrings that are the structural parts of the script.

Steps

  1. Comments