Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
feature: next generation of outfile format #1664
The outfile format has much potential, but we need a new way to express it.
The current method consists of IDs like the following:
This method has worked well up to this point, but growing beyond it will be increasing difficult. Adding just a single additional field would be very expensive, as it would require many new additional outfile format IDs.
Instead, I propose a new way to express outfile format fields - one that is extensible, using "variables" for the components.
My suggested approach:
(These are just for demonstration purposes - there may be better variables. That being said, I suggest shorter variables for easier typing).
This method will allow new "variables" to be more easily added later, without having to add a large number of additional outfile formats.
All current outfile formats would be expressed in the new syntax as follows:
Syntax would now be
For ease of parsing, only formats containing alpha, digits, and colons would be accepted.
These are rough and would need to be improved a bit.
And then perhaps a few more, brainstorming:
... or similar.
I realize that some of these would be of limited use at first. But I believe that distributed tools like Hashstack, Hashtopolis, etc. could use them, especially for analyzing multiple runs of information later. They would also support loose collaboration in teams, such as during contests.
I think that there is much potential that would be made possible by this change, and projects and teams could be creative with it.