I would get rid of that as quickly as possible

Issue #4 resolved
Peter Steinbach created an issue

Comments (4)

  1. Neelakandan Ramachandran

    @psteinb The API's declared here are in conformant with the cuffT counterparts. This was intentionally done so as to have a common API conformance with that of cufft.

  2. Neelakandan Ramachandran

    The hcfft API's almost conform to cufft spec. Not sure if having or removing the reference would imply anthing more

  3. Peter Steinbach reporter

    hi to all, this might be so ... but having an URL in your header files that look like you copy&pasted the cufft headers (wouldn't that violate the cufft EULAs?) does speak a thousand words about the efforts put into hcfft. further, it might give your competitor's legal department ammunition that you don't want them to have, but IANAL.

    thanks for removing that so quickly - peter

  4. Log in to comment