I can't fix a problem you have, if you can't tell me how to reproduce it. If you imply that everyone should check their changes for compatibility with MSVC, then I will be strongly against supporting MSVC and any environments other than MinGW because then it's more trouble than it's worth. I will of course assist in finding solutions for any problem that arises due to my contributions, but it is my opinion that support for these environments should be maintained by those who have and use them. The problems that can arise from patches not being compatible with MSVC are new problems. They didn't exist before some developers decided to support MSVC. I would also expect that those who port ReactOS to other architectures and have the hardware will maintain these ports, so that all other developers on the project don't need to verify that their changes work on these architectures. Every time support is added for a new environment or a new architecture the work required maintain ReactOS is increased. It seems only fair that those who want to support a particular feature also do most of the work to support that feature. Most, if not all major projects do it this way and for a good reason - it is the most efficient way.
Casper
-----Original Message----- From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Alex Ionescu Sent: 26. november 2005 02:06 To: ReactOS Development List Subject: Re: [ros-dev] Re: [ros-diffs] [chorns] 19566: Speed up compilationofntoskrnl
Casper Hornstrup wrote:
They shouldn't, but I don't build ReactOS with MSVC so I couldn't say for sure.
Casper
I don't want to seem like I'm criticizing you, but I hope that the attitude toward the MSVC backend won't be ' I won't use it so I don't care if I break it"...
Best regards, Alex Ioenescu _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev