Hi!
Somehow NtUserGetWindowThreadProcessId was moved to the main list.
This is wrong! With in the next six months
NtUserGetWindowThreadProcessId (unless it was added in Vista) and
friends will no longer be in ReactOS. Please do not create more work
than it is necessary to accomplish this rewrite.
-# ReactOS only system calls
-NtUserAcquireOrReleaseInputOwnership 1
-NtUserGetWindowThreadProcessId 2
-NtUserGetQueueStatus 1
Thanks,
James
Hello
I want port some function from wine kernel32.dll to ReactOS
kernel32.dll but have some problems.
First i have two modules and the question is where is the right place
to put them.
I need /tools/unicode/wctype.c also here /dll/win32/kernel32/misc/ to
compile.
1.) Is it better to leave this module in /tools/unicode/ ?
-> What must i write in kernel32.rbuild to build this module
with kernel32.dll
2.) or copy this file to /dll/win32/kernel32/misc/
the second solution is a bit ugly because we have tow files whit the
same contents.
3.) ???
thanks
Daniel
________________________________________________________________________
More new features than ever. Check out the new AIM(R) Mail ! -
http://webmail.aim.com
Alex wrote:
>On 26-Jan-08, at 2:34 PM, Marc Piulachs wrote:
>
>> Hi,
>>
>> I'm not very sure about r32018-r32022.
>>
>> Some compiler warnings are stupid and useless, some others not.
>
>This one is stupid.
Actually, I'd say the stupidity is in using a runtime assert, when a
compile-time assert will do the trick (not using CPU at runtime, while
enforcing the condition).
Unless memory fails me, in C++ you can implement ct_assert(x) like:
typedef char[x!=0] foo;
as an array of size zero is an error.
How does current C compilers react to typedefs of zero-sized arrays?
Sure, one can't use it exactly as in C++, but it could still be useful
to at least know about this idiom.
Problems should be trapped as early as possible.
--
Mike
>
> I think the "fixme" in halx86/mp/apic.c line 583 is no need to fix,i have
> > read the linux source code ,which just configure like reactos.So still
> > need to fix?
>
>
>