Skip to main content

parsing go templates

Given a template file I want to parse out some variables so that I can prompt the user but I do not want to build my own parser or some set of regex although after playing with the go templates and parse tree it might be the best thing to do since I'm already making the syntax simple.


My simple document looks like this:

doc := "fred {{.Fred}} barney"



Here's my sample code (playground):

package main

import (
"html/template"
"log"
)

func main() {
doc := "fred {{.Fred}} barney"
t := template.Must(template.New("sample").Parse(doc))
log.Printf("%#v", t)
log.Printf("%#v", t.Tree.Root)
log.Printf("%#v", t.Tree.Root.Nodes)
for _, n := range t.Tree.Root.Nodes {
log.Printf("%#v", n)
if n.Type() == 1 {
log.Printf("%s", n)
}
}

}


The output was interesting but as I expected and similar to the sort of parsing I was thinking about and was demonstrated by Rob Pike in his Lexer video. The downside of using the template parser is that it's going to parse a lot more than the simple (did I say that again) DSL I had in mind even though it's based on the go templates.

This is the logging that I performed before the for look. There is nothing particularly interesting here.

2009/11/10 23:00:00 &template.Template{escapeErr:error(nil), text:(*template.Template)(0x105345c0), Tree:(*parse.Tree)(0x10583a40), nameSpace:(*template.nameSpace)(0x10538360)}
2009/11/10 23:00:00 &parse.ListNode{NodeType:11, Pos:0, tr:(*parse.Tree)(0x10583a40), Nodes:[]parse.Node{(*parse.TextNode)(0x105346e0), (*parse.ActionNode)(0x10534740), (*parse.TextNode)(0x10534760)}}
2009/11/10 23:00:00 []parse.Node{(*parse.TextNode)(0x105346e0), (*parse.ActionNode)(0x10534740), (*parse.TextNode)(0x10534760)}


Here are the 3 nodes that were parsed. It essentially comes down to "fred", "{{.Fred}}", " barney". Since I was only interested in the actionnode I checked for it Type()==1 and then printed the name. I thought that I might get the inner part but then I realized that the parser need to look inside and pull more tokens out... the template schema is a DSL unto itself.

2009/11/10 23:00:00 &parse.TextNode{NodeType:0, Pos:0, tr:(*parse.Tree)(0x10583a40), Text:[]uint8{0x66, 0x72, 0x65, 0x64, 0x20}}
2009/11/10 23:00:00 &parse.ActionNode{NodeType:1, Pos:7, tr:(*parse.Tree)(0x10583a40), Line:1, Pipe:(*parse.PipeNode)(0x1053a1b0)}
2009/11/10 23:00:00 {{.Fred}}
2009/11/10 23:00:00 &parse.TextNode{NodeType:0, Pos:14, tr:(*parse.Tree)(0x10583a40), Text:[]uint8{0x20, 0x62, 0x61, 0x72, 0x6e, 0x65, 0x79}}


There is a lot of stuff in the parsed doc. It might be simple to locate the pieces I'm looking for. But this is a start.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

Agile is still dead and has been since 1991

[updated 2011.09.30] yet another response to Agile is good.
When you have so much of you career invested in something like Agile, XP etc... it can be hard to see the forest for the trees. I had a consulting job in The Haag many years ago. IBM was the incumbent contractor at the customer site (a bank) but after 5 years on the job they had not written a single line of functioning code. In the office there were two teams of software people... both behind closed doors. The first team was the Data team and the second team was Functional. They rarely spoke and they never shared information. I was there for a week, introduced the client to OO and we had a functioning prototype. Smart people do smart things, You cannot make an underachiever exceptional by using Agile. Either they get "it" or they don't.
I just commented on a blog. I'm sure there is some validity to his post beyond observing that Agile Scrum is broken. It certainly is not what it was originally intended but for…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…