"jimtabor" <[EMAIL PROTECTED]> wrote:
Julien wrote:
/ I was very interested in comparing the implementation status of reactos
/>/ and wine. So I coded a little python script to list all the api that are
/>/ implemented in reactos AND are only stub in wine. Attached to this mail
/>/ is the lis
Julien wrote:
/ I was very interested in comparing the implementation status of reactos
/>/ and wine. So I coded a little python script to list all the api that are
/>/ implemented in reactos AND are only stub in wine. Attached to this mail
/>/ is the list of identified functions.
/>/
/>/ One
On 9/4/06, Brandon Mark Turner <[EMAIL PROTECTED]> wrote:
I think it would be nice if everyone just left this thread alone for now.
You guys made up your minds that you don't want our patches. And thats
fine.But there is no reason to continue to express hateful opinions
about ReactOS.
I do
Dan Kegel writes:
I doubt the audit is completed yet (these things are asymptotic; you
can get to 90%
complete a lot faster than 99% complete, etc.).
I am not trying to be a jerk and I am not taking a shot at you personally.
I actually think you are a good guy Dan so don't take this the wr
On 9/4/06, Saulius Krasuckas <[EMAIL PROTECTED]> wrote:
BTW, can results of Wine's own audit process be seen somewhere on the web?
Good question. I don't know the answer, but I'll see if I can find one.
It would be nice to know at least what speed was Wine project audited and
when did it hap
> I'm afraid it's the other way around at this
> point - the burden of proof is on ReactOS to show
> that their code is clean :-(
A)-no offense, but this sounds like something SCO
would say. if you got something (from reactOS current
that is already audited..) that you can prove is
dirty- please
* On Mon, 4 Sep 2006, Dan Kegel wrote:
> * On 9/4/06, Saulius Krasuckas <[EMAIL PROTECTED]> wrote:
> > have you any proof of "all ReactOS code audit process being fake" ?
>
> The audit went awfully quickly, for one thing,
> and it was done without a neutral third party.
> Wine's been doing its own
On 9/4/06, Julien <[EMAIL PROTECTED]> wrote:
Sorry Mike but from an external point of view your argument sounds like
ideology:
1) I dont understand why someone contributing to ReactOS would have
his/her code rejected in all cases. Contributing to ReactOS does not
necessary means the code is "dirt
Sorry Mike but from an external point of view your argument sounds like
ideology:
1) I dont understand why someone contributing to ReactOS would have
his/her code rejected in all cases. Contributing to ReactOS does not
necessary means the code is "dirty" reverse engineering.
2) The author stressed
On 9/4/06, Saulius Krasuckas <[EMAIL PROTECTED]> wrote:
Well, Dmitry and Mike, this sound very probable, but have you any proof of
"all ReactOS code audit process being fake" ?
The audit went awfully quickly, for one thing,
and it was done without a neutral third party.
Wine's been doing its ow
* On Mon, 4 Sep 2006, Dmitry Timoshkov wrote:
> * "Tom Wickline" <[EMAIL PROTECTED]> wrote:
> > Looks to me like reverse engineered code is "not permitted for
> > inclusion in ReactOS" so how is it there participating in "dirty"
> > reverse engineering?
>
> That's just a declaration supposed to
"Tom Wickline" <[EMAIL PROTECTED]> wrote:
Looks to me like reverse engineered code is "not permitted for
inclusion in ReactOS" so how is it there participating in "dirty"
reverse engineering?
That's just a declaration supposed to create a better face on public,
nothing more to take it seriousl
On 9/3/06, Mike McCormack <[EMAIL PROTECTED]> wrote:
Code that originates in ReactOS will generally not be accepted into Wine
due to that project's acceptance of developers that participate in
"dirty" reverse engineering (ie. translating assembly code to C).
??
From : http://www.reactos.or
Julien wrote:
I was very interested in comparing the implementation status of reactos
and wine. So I coded a little python script to list all the api that are
implemented in reactos AND are only stub in wine. Attached to this mail
is the list of identified functions.
One may note that most of
Hello all,
I was very interested in comparing the implementation status of reactos
and wine. So I coded a little python script to list all the api that are
implemented in reactos AND are only stub in wine. Attached to this mail
is the list of identified functions.
One may note that most of these
15 matches
Mail list logo