;line1
;line2
;(;mline1
mline2
mline3;);to something end
to setup
print "\x45\o123\u6d4b\u{08bd5}\n\s"
print """#(;
{
"code":"200",
"status":200,
"msg":"",
"body":{
"time":;)#[timer]#(;
}
}
;)"""
end
to startup
setup
end
生成代码:
;line1
;line2
;mline1
;mline2
;mline3
to something end
to setup
print "ES测试\ns"
print (word """\n {\n \"code\":\"200\",\n \"status\":200,\n \"msg\":\"\",\n \"body\":{\n \"time\":"""timer"""\n }\n }\n """)
end
to startup
setup
end
Hey John, I’m not sure what this question is, can you elaborate on what you mean?
For the rest, these would be changes to the core NetLogo parser. We had an open issue for string interpolation. Surprisingly we had no open issues for multi-line strings or multi-line comments. I went ahead and opened them. Note that opening them doesn’t mean we will implement them, just that it’s a proposed enhancement.
I was refering to the fact that @maizi20 is trying to work on a custom transpiler that implements the grammar before we ever started.
That said, to maintain compatibility, maybe we could first come up with a draft grammar as a way both to support the user-lead effort and to keep our language consistent in the long run.