Questions for developing functions

David Elliott dfe at tgwbd.org
Sun Jan 20 13:07:29 CST 2002


On 2002.01.20 12:46 Gerhard W. Gruber wrote:
> On Sun, 20 Jan 2002 11:38:48 -0500, David Elliott <dfe at tgwbd.org> wrote:
> 
> >Well, if the code you contribute could be considered a derived work of
> the
> >code you disassembled then you'd have problems.  But for instance if you
> 
> >disassembled for the purposes of figuring out how many arguments the
> >function takes and what not but didn't actually directly write your code
> 
> >based on the disassembly, then you should be in the clear as far as that
> 
> >is concerned.
> 
> Of course I primarily use that insight to get information on what
> arguments
> are used. I don't intend to make a 1:1 representation of the binary code
> to C.
> :)
> 
> >Now, as for the breaking of the license agreement on your software.
> That
> >mostly concerns you as you are the person under the license, not the
> Wine
> >project.  So if you feel like you would get into legal trouble by even
> >disassembling something to simply see what types of parameters it takes,
> 
> >then I would suggest that you didn't do it.  However if you feel that
> you
> >would not get into legal trouble, and assuming you don't create your
> >implementation directly from the disassembly (i.e. you reimplement from
> >scratch, but just use the disassembly to get some ideas of function
> >parameters) then you should be very much in the clear, and so should the
> 
> >wine project.
> 
> Thanks. :)
> 
Remember though.. I am not a lawyer, and I am not Alexandre Julliard.

> >Hey man, if no one responds in this mailing list within a reasonable
> >timeframe then probably no-one is working on it.  Just have a go and if
> >someone else beats you to it without saying anything you can always do a
> 
> >peer-review of the code and see if maybe something should be done
> >different.  Two pairs of eyes are better than one.
> 
> OK. Sorry to bother you with this, but I'm just starting out, so I don't
> know
> much about the procedure on how to contribute a bit. :) I'd also hate to
> start
> investingating when a few days later a patch is thrown at the list that
> does
> what I just started out to do. :) I also think that it wasted time on
> behalf
> of wine if many developers work on the same things and leave other areas
> to
> its own.
> 

No, it's not a bother.. the fact that you just posted saying that you were 
gonna work on it is desirable.

-Dave




More information about the wine-devel mailing list