Hello,
I am sorry for my ignorance, but has there been any discussion on these features to go to gemlib?
AFAIK, no discussion... oh yes!, an "open discussion" where i pointed out some important problems, and the discussion ended with "goodbye" without any reply to the point i highlight.
I would rather see some sort of a consensus on each particular new extension of AES before it gets to the the only up-to-date library bindings.
Me too :)Now, i wonder what's the best way : create a new branch in XAAES and remove the WCOWORK feature, or no more support XaAES in our developpments... or just change the main branch of XAAES (no need to discuss and get common agrement if i correctly understood).
This is not a problem of backward compatibility, this is a problem of death of the ongoing hudge work we started since years now in order to have a modularity approach of programming for *futur* AES applications.
Please open your eyes ! Wake up ! You're not the only one having ideas for the futur, and i don't understand why you want to kill our work (please gets the facts and list the real benefit of WCOWORK... it's really ridiculous).
BTW, i do not agree on the stuff written in newcall.txt about WCOWORK. All the lines usually written with 2 pix heigh font at the bottom of the page are missing here.
best regards, Arnaud.