чт, 21 нояб. 2019 г. в 22:22, Niels Möller nisse@lysator.liu.se:
Dmitry Eremin-Solenikov dbaryshkov@gmail.com writes:
During this rework I thought about switching ecc_point from bearing just x and y coordinates to have per-curve defined coordinates (like projectile or inverted).
Struct ecc_point is intended to be a public api, which should be independent of the implementation's preferred representation. So just two numbers x, y.
ecc_point_set/_get() are fine from my point of view. I was working on internal ecc_point representation (w/o size changes).
Basically I have two strange curves which are defined in Weierstrass form, but have equivalent Untwisted Edwards form. I planned to make ecc_point_set/get convert between x,y and u,v,w (and to store these coordinates in ecc_point). To make things easier I also changed secp curves to store x,y,z in ecc_point.