[Bug 50464] Process Hacker 3.x needs ntdll.dll.RtlGetFullPathName_UEx

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50464

--- Comment #7 from Ben Shefte <shefben at gmail.com> ---
I'm a little confused with what you are saying.  The WineHQ wiki says for
obvious reasons: don't look at or use any leaked code.  Understandable,
especially because its illegal. The wiki also says Google is our friend.

But from what I read; ReactOS was within legal limits with its work.. The
articles  I have read could be wrong i guess. I also was under the impression
both Wine and ReactOS worked closely together.

But that leads me to an interesting problem/question:  How could wine have
gotten as far as it has without ANY disassembly?  I know ms documentation gives
SOME information.  But If everyone was being honest; how many of the patches
people add are not from disassembled code? 

My thing is, if I use information from some place; I add the URL to my patches.
How many of the people who submit patches do the same? i.e. Link to the things
they referenced?  Very little from what I have seen on
https://source.winehq.org/patches/

It is the exact reason I wont submit patches through there, I feel as though
everything I do will get shot down; so I just wait for someone else to submit a
patch that is up to standards there.

I understand The legal implications to it, but I am confused at where the line
is drawn when it comes to looking for information on google (which your WIKI
does recommend)  and how you can be certain some code you find is not
disassembled (I'm not talking about code that is mostly inline (dis)assembly
for obvious reasons)

I just want the WIKI to be MUCH more definitive/precise on what IS and IS NOT
allowed.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.