|
From: Stephen W. <st...@ic...> - 2014-11-12 16:38:43
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think vvp/vpi_darray.c is safe enough for you to work in right now. Remind me what specifically you are trying to add? I remember that I approved of what you're doing, but a quick reminder what that is exactly will help me. Sometime soon, I'm going to want to merge the vec4-stack branch into the master branch, so that may turn my distraction into everybody's distraction;-) On 11/12/2014 08:31 AM, Maciej Sumiński wrote: > Hi Steve, > > As far as I could see, there are no VPI functions to access > dynamic arrays contents and that is a dependency for my further > work. I have already started implementing the missing bits, ending > up with code that resembles the part that handles standard arrays. > To avoid code duplication, I would like to use templates for a few > functions or create a common ancestor class. > > You have recently mentioned that you are in the middle of vvp > rework. I do not want to cause too many conflicts, therefore I ask > - do you think it is safe to modify vvp/vpi_darray.c & > vvp/vpi_priv.h? For the time being they seem to be untouched in > vec4-stack branch, but I would rather get a green light from you. > > Regards, Orson > - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlRjjQkACgkQrPt1Sc2b3inCzACeJn+H+HfeePpbE87OT4EtITV9 Ig4AoK8QFS0oo31d2+1DMXB8RZlmSWKc =lugz -----END PGP SIGNATURE----- |