>Porting a codebase the size<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
>of Wine will probably take years... <br><br></div>Actually I'm working on a program to convert C code to D code. You can find/replace most instances of code, like unsigned int (C) with uint (D). The import/include files might take some work though.<div>
<div></div><div class="h5"><br>
<br><div class="gmail_quote">On Wed, Jun 23, 2010 at 2:46 PM, Gert van den Berg <span dir="ltr"><<a href="mailto:wine-devel@mohag.net" target="_blank">wine-devel@mohag.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>On Wed, Jun 23, 2010 at 20:48, Stephen Eilert <<a href="mailto:spedrosa@gmail.com" target="_blank">spedrosa@gmail.com</a>> wrote:<br>
> On Wed, Jun 23, 2010 at 3:06 PM, Christopher Selph <<a href="mailto:cds.wine@gmail.com" target="_blank">cds.wine@gmail.com</a>> wrote:<br>
>> Well, being a garbage collected language, it would help with the memory<br>
>> leaks in Wine. Being OOP it could extend the design of the code to make it<br>
>> cleaner and reusable.<br>
><br>
> The assertions above are opinions, not facts. Also, it requires a full rewrite.<br>
><br>
</div>You can mix D code and C code...<br>
<br>
A more modern language can result in more readable code, but it is a<br>
lot of effort for a small benefit... (And D is a very new language,<br>
possibly to the degree that portability might be impacted due to a<br>
lack of compilers on some of the more obscure platforms /<br>
architectures).<br>
<br>
Certain parts of Wine might benefit from the latest (draft) version of<br>
C++ and the size of the codebase can probably be reduced in size<br>
slightly, but a bad port to another language doesn't help anyone...<br>
(The C++ standard library is huge and might getrid of some POSIX<br>
dependancies) It might require quite an extensive rewrite to get it to<br>
a proper C++ program, rather than a C program containing a bit of C++<br>
and compiled with a C++ compiler...<br>
<br>
Fixing the current problems with Wine should be a much higher priority<br>
than porting it to a different language... Porting a codebase the size<br>
of Wine will probably take years... C can do anything that other<br>
languages can, the amount of effort might differ a bit, bit the<br>
difference is probably minor compared to familiarizing yourself with a<br>
new language, new libraries, etc....<br>
<br>
(I like D - it have most features from languages like Java and C#,<br>
with the option to switch off things like garbage collection and it<br>
compiles to native code... Experimenting with it for new project might<br>
make sense)<br>
<br>
(IMHO: Allowing other languages than C for some of Wine's bundled<br>
applications (notepad, winecfg, winemine, etc) might make sense, as<br>
long as the QC for committing patches doesn't suffer. The mixing of<br>
languages within components (single application / DLL) will probably<br>
cause confusion and ugly code though... Getting proper QC would<br>
probably mostly involve sticking to things that AJ is familiar with.)<br>
<font color="#888888"><br>
Gert<br>
<br>
<br>
</font></blockquote></div><br>
</div></div></blockquote></div><br>