first answer there provides a good overview of key differences.
Best regards,
Aleksey Bragin
On 06.11.2012 15:44, Pierre Schweitzer wrote:
Hi,
Don't worry, you'll probably don't catch any difference in the way the C
code is handled.
I also take the opportunity of this answer to announce that I enabled
syntax highlighting on Doxygen output. Code should be more readable now.
With my best regards,
Le mardi 06 novembre 2012 à 09:57 +0100, Timo Kreuzer a écrit :
> We have 90 % C. So disabling OPTIMIZE_OUTPUT_FOR_C will probably result
> in worse readable output for 90% of the code.
>
> Am 05.11.2012 12:14, schrieb pschweitzer(a)svn.reactos.org:
>> Author: pschweitzer
>> Date: Mon Nov 5 11:13:59 2012
>> New Revision: 57674
>>
>> URL:
http://svn.reactos.org/svn/reactos?rev=57674&view=rev
>> Log:
>> [DOXYGEN]
>> ReactOS is not C only.
>> Enable support builtin STL.
>>
>> Modified:
>> trunk/reactos/Doxyfile
>>
>> Modified: trunk/reactos/Doxyfile
>> URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/Doxyfile?rev=57674&r1=…
>> ==============================================================================
>> --- trunk/reactos/Doxyfile [iso-8859-1] (original)
>> +++ trunk/reactos/Doxyfile [iso-8859-1] Mon Nov 5 11:13:59 2012
>> @@ -196,7 +196,7 @@
>> # For instance, some of the names that are used will be different. The list
>> # of all members will be omitted, etc.
>> -OPTIMIZE_OUTPUT_FOR_C = YES
>> +OPTIMIZE_OUTPUT_FOR_C = NO
>> # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
>> # sources only. Doxygen will then generate output that is more tailored for
>> @@ -236,7 +236,7 @@
>> # func(std::string) {}). This also make the inheritance and collaboration
>> # diagrams that involve STL classes more complete and accurate.
>> -BUILTIN_STL_SUPPORT = NO
>> +BUILTIN_STL_SUPPORT = YES
>> # If you use Microsoft's C++/CLI language, you should set this option to
YES to
>> # enable parsing support.
>>
>>
>>
>
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org