On Thu, 26 Sep 2013, Riccardo (Jack) Lucchetti wrote:
*Perhaps* the right sequence of steps, if we want to minimise the
fallout is:
- introduce, as an experimental feature, the printf function asap, and start
using it internally as soon as possible (for example, in the sample scripts,
or in addons)
Yes, agreed.
- introduce the new tokenizer supporting the printf command (of
course,
provided it isn't to difficult to fit existing syntax into it; Allin?)
It can be made to work.
- provide some way (the more the better), to sanitize existing
scripts: the
equivalent to the python gadget Sven was referring to. This shouldn't be too
hard to do once the tokenizer is proven and robust. It could be a stand-alone
app, or even, maybe, an online thing: you upload the "printf-as-a-command"
inp/gfn file(s) and download the sanitized "printf-as-a-function"
corresponding file(s). Before you say it's overkill, an infrastructure like
this would make it viable to think of even bolder changes for 2.0.
Yes, that had occurred to me too -- well, the stand-alone program idea
anyway. The online script-updater is also a nice idea, and would be easy
to do given the program.
Allin