Volker, the answer to the balance question. My formatting is that "«balance
(2:1) [0:0] {1:0}»" gives the number of left and right parenthesis, lefdt
and right brackets, and left and right braces in using
":":
2019/06/16 17:57:59.844755 files that failed the Go lexical scan:
2019/06/16
The "src" subdirectory of go does balance, but building every ".go" file in
./go does lose the balance. I sensed your discomfort so I've changed my
plans a little to take as day to make a flexible command line tool out of
my go-test so that with it's verbose mode you'll know which files have
On Wednesday, 12 June 2019 23:48:36 UTC+2, Michael Jones wrote:
>
> Volker, did you see a few posts back that I did the run Roger asked about,
> on RSC’s huge corpus? It is about 10x the size and its parens, braces, and
> brackets match just fine, all *7476284* of them
>
If I remember the
Volker, did you see a few posts back that I did the run Roger asked about,
on RSC’s huge corpus? It is about 10x the size and its parens, braces, and
brackets match just fine, all *7476284* of them
On Wed, Jun 12, 2019 at 2:13 PM Michael Jones
wrote:
> They matched up until yesterday. When
They matched up until yesterday. When I updated at 2am California time it
changed. It also had no "0o" octal literals up until the latest.
I'd planned to joke how the race was on to be the first to check in a new
octal literal in my mail, but a few of those snuck in too.
Yesterday:
Count |
Cool work!
What I found most astonishing on a first look: Not all
parentheses ( are closed: 4 ) seem to be missing??
For { 5 are unclosed while there is one more ] than [ ?
Are you parsing testfiles with deliberate errors?
V.
On Wednesday, 12 June 2019 15:08:44 UTC+2, Michael Jones wrote:
>
>
