Quote:
Originally Posted by elit
Regarding '+' and ',' characters issues, why not just use ':' for everything and dissect the parameters in the code instead? I mean, for example:
Code:
xtool -mzlib:c32mb:reflate:l9
^This is perfectly easy to scan because names like zlib, kraken, reflate etc are unique and cannot appear as codec flags. So in your code you would just look for a word that represent a codec in the list and then all other params would be flags until next codec name is detected. So for example:
Code:
-mzlib:kraken:{param}
program would still know that zlib is with default parameters and kraken with whatever you put behind it simply because it knows about reserved words.
Also regarding versioning, whats wrong with simple v1.032, v1.033, v1.034 or anything like that?
Just a suggestions of course, I don't want to feel ungrateful or anything. |
regarding character parsing, I could change it but the thing is, xtool doesn't really know reserved words because there are none but I can change it if that's what people want.
The reason I went with a versioning like this is because the there are already 3 different xtools so to not confuse people, they should just check the YYMM it was released on as the old xtool, 0.0.19... has special editions from the request of repackers so basically the versioning is so confusing so I then decided I'd only adopt it once I think the project is a guaranteed success. 2019 is an example because what I tried to do fail, so I tried again with 2020 to see if it will work with little hope of success but as soon as it seems like the idea of external plugins is possible and can be done without bugs then versions will be brought back.