Two years ago, I compiled csound 4.23 with both Visual C++ version 7.0, and 
the then current version of MinGW/gcc version. Csound rendered "Trapped in 
Convert" at almost exactly the the same speed with both versions. At that 
time, MSVC++ was supposed to be faster than gcc, but it was not so with 
Csound. Since then, both compilers have improved in speed.

Magazines print tests showing MSVC++ version 7.1 to be somewhat faster than 
gcc 3.4.2 (the current versions), and the Intel compiler to be somewhat 
faster than MSVC++ 7.1. But perhaps it is still not so with Csound.

----- Original Message ----- 
From: "Richard Dobson" 
To: 
Sent: Sunday, January 30, 2005 6:09 AM
Subject: Re: [Cs-dev] Csound 4 is not ANSI C89


> Viusual C++ v6 does not support it, and I have now checked the free 
> download of Visual C++ 7, and that does not support it either (no stdint.h 
> anywhere, nor are the types defined anywhere else). I have yet to try the 
> beta of Visual C++ .NET 2005 (demands more space than my spare machine can 
> supply), but even if that does support C99 (and assumning it is not 
> modified or "extended" in some way), many developers are likely to stick 
> to v7, or even v6 for some time yet. Indeed, having found that even the V7 
> optimiser still generates astonishingly pathological instant-crash code 
> for one particular program of mine, while the Intel compiler generates 
> correct/efficient/compact code, I am currently rather more likely to 
> upgrade to the Intel compiler than VC vX; and that does not support C99 
> either as far as I can see!
>
> So I think we will want to stick to ANSI for the forseeable future. At the 
> very least, given the new dependence on plugins, we would want to be sure 
> C99 modules can link to C89 ones, and the introduction of new types into 
> c99 would seem to preclude that, except where the C99 modules are ANSI 
> compliant anyway.
>
>
>
> Richard Dobson
>
>
>
> Istvan Varga wrote:
>> John D. Ramsdell wrote:
>>
>>> I noticed that csound/ccsound.c was not ANSI C89, so I tried compiling
>>> the Csound 4 source using GCC with -ansi.  I found out there are many
>>> parts of Csound 4 that are not ANSI C89.  The file csound/aifc.c
>>> contains multi-byte characters, but worse, csound/csound.h uses C++
>>> style one line comments--a C99 feature.  I fixed csound/ccsound.c,
>>> but did not touch anything else.
>>
>>
>> Would it be possible to switch to C99, at least in Csound5 ? It has
>> many useful features compared to C89. How many people use compilers
>> that still do not support C99 ?
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
>> Tool for open source databases. Create drag-&-drop reports. Save time
>> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
>> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net