Dennis Schridde schreef:
> Am Montag, 8. Januar 2007 19:43 schrieb Christian Ohm:
>
>> I see several advantages to a public branch compared to working just on
>> a local copy:
>>
>> - Other people have the chance to comment, test, report bugs, help with
>> coding... (impossible if noone knows what you're doing).
>>
>> - Smaller changes. On a local branch you can only make one big patch
>> that has to work (more or less) before being applied. A SVN branch
>> records your steps while working, enabling people to follow your work,
>> and understand the new code easier, as well as giving more
>> fine-grained changes to look for eventual bugs.
>> (Of course you can use a local revision control system to work with
>> and record your patches, and when it all works, apply those
>> subsequently to SVN. But that's more work, and you lose the "time
>> factor" that let's people follow your progress.)
>>
>> I am not saying that this will happen with a public SVN branch, but with
>> a local branch, it can't even happen.
>>> My experience from work, where I maintain a large codebase of mixed C
>>> and C++ code, is that such mixing is a maintenance nightmare. I do not
>>> want this unless there is a very good reason for it, and what you are
>>> providing are arguments to convert all of Warzone to C++, which, even
>>> if you buy those arguments, is a totally different discussion.
>>>
>> Hm, and the current code isn't a maintenance nightmare? I think using
>> some C++ to encaspulate stuff will make things better, not worse (if
>> done right, of course, but you can write bad and good code in both C and
>> C++). That might be possible with C as well, but to me it seems more
>> natural in C++.
>>
>> What I don't agree with is making a C interface to a C++ interface to
>> OpenAL - seems like duplicated work to me. I'd just use C++ in the code
>> and compile the complete game with a C++ compiler. But that's just me, I
>> guess there needs to be some decision about how to use C++, or we just
>> follow the usual "those who do decide" approach.
>>
> Basically I think that's the maintainance problem...
> Actually I didn't even know that it is possible to link a C application
> against a C++ lib, because I thought the C++ ABI is incompatible to the C
> ABI...
>
In fact OpenAL itself is written largely in C++. They simply wrapped its
interface (or more accurately the include files with function
declarations) in an extern "C" {...} declaration to make sure the
compiler generates C-style symbols which can then be resolved by the
linker when linking with C-code.-- Giel
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
