A89: Re: Re: Re: Re: Re: Re: Re: Re: CORRECTION: Shift+ON
[Prev][Next][Index][Thread]
A89: Re: Re: Re: Re: Re: Re: Re: Re: CORRECTION: Shift+ON
> descriptions is a stealing. And see this problem: I have an
> information (discovered by me) about 150-200 new functions,
> and I can not publish them. Why? Publishing them need a
> month of work for me, and after this, I can not prove that
> these informations are product of my researching.
I have been staying out of this debate for a while, since though I am still
interested in TIs and stuff, my not actually having a real TI-92+/89 and
being very busy, my calc programming time is quite limited.
But, in response to your dilemma here, why don't you write all the
descriptions you possibly can quicklyin your own language, and then release
that document. It is still proof of your knowledge of the functions,
because it can be translated and read by anyone with knowledge of your
language. And its public release date can be proven in a court of law. And
therefore, you can prove that you knew all the stuff you know before you
began testing the SDK.
So, then you can translate that document at your leisure, including updated
the library and such. Because then you could prove that all information you
know about it comes from your own hard work.
Just a few thoughts,
--kaus
References: