Plan for up-coming changes

[suntong]

I'm planning the following up-coming changes

• will support .json data as well as the .yaml data
• most importantly, I'm planning to make none-backward-compatible breaking changes to the easygen command line option. The reason is that, the more I use easygen, the more cases that I find that I'm using the same template with different driving data. I.e., previously in my mind, the driving data is the most important, but now I realize that the template is more important.

So, I'll be changing the easygen command line option as follows:

easygen [options] template_name [data_filename [data_filename...]]

So,

• If only template_name is given, then the data_filename will be derived from the template_name. I.e., reverse the current behavior. So for the existing usage of easygen filename, when filename does not specify the extension. It'll still work, without any changes.
• for the current usage of easygen -tf name YamlFileName (or easygen -tf name f1 f2 etc), the new usage will be easygen name YamlFileName. I.e., there won't be the -tf option any more.

@grrtrr, what do you think?
Also, as the change is only at external command line option level, not at the software API level, do you think we should bump up the new change to version 4, or maybe 3.1 is good enough?

thx

[suntong]

Moving forward as version 4...