View Single Post
Old 05-31-2016, 04:19 PM   #30
ApK
Award-Winning Participant
ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.ApK ought to be getting tired of karma fortunes by now.
 
Posts: 7,393
Karma: 68715774
Join Date: Feb 2010
Location: NJ, USA
Device: Kindle
Quote:
Originally Posted by rkomar View Post
Yes. An API is usually implemented as header files, which are meant to be embedded into other people's code (i.e. to be copied). Making them illegal to copy by default seems to go against the whole point of publishing the APIs.
That's not a relevant comparison.
The question of whether implementing an identical API should be allowed is, I think, orthogonal to how other systems interface with the API.

As an aside, I'd argue with the "usually" aspect of header files. There are plenty of APIs where the concept of a header file simply wouldn't apply, that have no source component at all, no SDK, barely any documentation....
ApK is offline   Reply With Quote