sginsberg(a)svn.reactos.org wrote:
> Author: sginsberg
> Date: Wed Jun 17 16:44:05 2009
> New Revision: 41436
>
> [...] Because gcc is awesome we can then check for debug compilation with both #ifdef DBG and #if DBG (error free! yay gcc!), and so we have mixed usage all over the tree
MSVC behaves exactly the same way ;-P
I forgot to add to the commit message for r41520 that I lowered the
warning level of Visual C++ from -Wall to -W1. This will let us fix the
most serious compatibility issues first. Remember: set ROS_RBUILDFLAGS
to -dd -Mcmsc, and make --keep-going is your friend. Now go, and make
awesome things with this!
timo.kreuzer wrote:
>This is what I found:
[...]
So, essentially, what you found is that all versions you looked at,
did indeed define va_list if <stdarg.h> was included?
--
Mike
timo.kreuzer wrote:
>In recent ms crt headers, va_list is defined in crtdefs.h,
Also in vadefs.h (at least for VC8), which is then (obvious) included
by <stdarg.h>.
Do you have an example of an MS env. where including stdarg.h does not
define va_list?
--
Mike
On Tue, Jun 16, 2009 at 11:41 AM, <dchapyshev(a)svn.reactos.org> wrote:
> Author: dchapyshev
> Date: Tue Jun 16 19:41:29 2009
> New Revision: 41424
>
> URL: http://svn.reactos.org/svn/reactos?rev=41424&view=rev
> Log:
> - Add Symbol font from Wine
Thank you. This will save us a LOT of trouble later with Office applications.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
hyperion(a)svn.reactos.org wrote:
> Author: hyperion
> Date: Tue Jun 16 04:24:26 2009
> New Revision: 41421
>
> URL: http://svn.reactos.org/svn/reactos?rev=41421&view=rev
> Log:
> modified dll/win32/srclient/srclient_main.c
> What the hell, Arch Blackmann? <windef.h>, <winbase.h> and <winnls.h> are not meant to be included directly. Include <windows.h> instead
>
> modified drivers/video/font/ftfd/rosglue.c
> Move standard C includes before Windows includes, so the required types are defined beforehand
>
> modified include/crt/_mingw.h
> Re-add Visual C++ support
> va_list is not a built-in type, it does not belong in _mingw.h
> Do not include intrin.h (screw you, Arch)
> Removed definition of _USE_32BIT_TIME_T ("ROS HACK!")
>
> modified include/crt/conio.h
> modified include/crt/stdio.h
> modified include/crt/wchar.h
> Pull in va_list from stdarg.h
>
In recent ms crt headers, va_list is defined in crtdefs.h, so it's
defined by all headers. This might not fit ANSI C, but that's what ms
does. So for compatibility reasons we might want to do it the same way(?)
On Jun 13, 2009, at 9:25 AM, cgutman(a)svn.reactos.org wrote:
> Author: cgutman
> Date: Sat Jun 13 09:25:54 2009
> New Revision: 41399
> +UCHAR
> +EXPORT
> +NdisGeneratePartialCancelId(VOID)
> +{
> + static UCHAR CancelId = 0;
> +
> + CancelId++;
I don't think using static var for this purpose is a great idea.
WBR,
Aleksey Bragin.
aicommander wrote:
[...]
>The main problem with NDIS 5.1 drivers is the lack of S/G support in
HAL
> (PRO/100 and PRO/1000 XP drivers are affected by this).
Could the follwing info from public MSDN help? If so, it seems to be a
rather minor hack to make it work:
Scatter/gather DMA
Scatter/gather DMA is a shortcut method that sets up several
packet DMA transfers at once. If you are transferring a packet over the
network, for example, each part of the network stack adds its own
header (TCP, IP, Ethernet, and so forth). These headers are all
allocated from different places in memory. In this case, the
scatter/gather DMA saves time by issuing a batch request to the HAL to
map each header plus the data segment for access by the hardware.
Instead of having to call the packet DMA routines on each part of the
packet, this method calls each routine once, and lets the HAL be
responsible for mapping each one individually.
Note Scatter/gather capability does not mean that the device can
use the scatter/gather routines. Scatter/gather capability refers to a
flag in the device description that indicates that the device is able
to read or write from any area in memory, instead of just a certain
range.
--------
What I found to be the interesting (and easily hackable) part was "and
lets the HAL be responsible for mapping each one individually".
--
Mike