Re: PATCH limit warnings from doxygen
<[email protected]> Mon, 5 Jan 2015 09:49:37 +0000
| Newsgroups | gmane.text.doxygen.devel |
|---|---|
| Message-ID | <92FCCC3A04F6DB48B59CE5FEC2612A6B1D1DBD09@045-SN2MPN2-052.045d.mgd.msft.net> |
--_004_92FCCC3A04F6DB48B59CE5FEC2612A6B1D1DBD09045SN2MPN205204_
Content-Type: multipart/alternative;
boundary="_000_92FCCC3A04F6DB48B59CE5FEC2612A6B1D1DBD09045SN2MPN205204_"
--_000_92FCCC3A04F6DB48B59CE5FEC2612A6B1D1DBD09045SN2MPN205204_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Dimitri
I hope you don't mind but I'm resending this to the develop list, this time=
with a smaller zip file as the previous one bounced the email from the li=
st and I am unsure if the list received the message.
The larger config.xml I removed, but outline the change needed here
-------------------------------------------------------
</docs>
</option>
<option type=3D'int' id=3D'LIMIT_WARNINGS' minval=3D'0' maxval=3D'10000=
' defval=3D'0'>
<docs>
<![CDATA[
The \c LIMIT_WARNINGS tag can be used to stop doxygen when a maximum number=
of warnings has been seen.
<br>
\b Tip: Turn warnings on while writing the documentation.
]]>
-------------------------------------------------------
Paul
From: Paul Hoad
Sent: 03 December 2014 12:57
To: '[email protected]'; '[email protected]'
Subject: PATCH limit warnings from doxygen
Dimitri
I recently posted a question on StackOverFlow regarding being able to stop =
doxygen after it had seen a certain number of warnings, somewhat akin to th=
e -ferror-limit=3DN option that certain compilers have.
http://stackoverflow.com/questions/27174031/possible-to-stop-doxygen-after-=
n-warnings
I have a large code base, mostly un-doxygen'd, I have a nightly build that =
runs doxygen but its produces thousands of warnings. I know getting full co=
verage is going to require a gradual continuous improvement approach which =
leads to a mindset change of the individual teams of developers.
So to tackle this I have added doxygen running on the current source subdir=
ectory as "PreBuild Event" in Visual Studio project files, I don't want to =
use the temporary documentation it generates (that will come from the full =
tree nightly build), but I want to see the warnings, I format the warnings =
with
WARN_FORMAT =3D "$file($line): $text"
Which this means that while the code is compiling, this allows the develope=
r to go back in and double click the warnings in the output window and be t=
aken to the location to fix those doxygen warnings (as they would any other=
warning), the problem is that for many of the directories the number of wa=
rnings is huge (which are too daunting to fix in one go)
I don't want to do a full Doxygen scan everytime (which is also why I only =
do it on the sub directory) because that will take too long and I don't wan=
t all the warnings or the developer will simply treat it a noise, I just wa=
nt them to see a few and then stop.
My idea is to be able to tell doxygen to document locally only a certain nu=
mber of warnings and then stop, this means that every build the developer w=
ill see a few more warnings (but only a couple 5-10) and be driven to fix t=
hose, over time the code will become documented and the developers will lea=
rn to document as they go, also any new code (especially in previously doxy=
gen clean areas) will immediately become a warning. Think of it as "Continu=
ous Incremental Documentation"
Given that I don't think this is possible currently, I took it upon myself =
to try and learn how to do it, I am very new to the doxygen source code, so=
I apologize in advance if I did it in the wrong place.
So the change to the doxygen source to implement something like this turned=
out to be fairly simple, with only having to add a new LIMIT_WARNINGS opti=
on to the config file, so I thought I would share the code change, feel fre=
e to use or discard as you see fit.
So I've not contributed before, so I'm not 100% clear of the etiquette or w=
ho to send any diffs to, so I've included the changed files and the diff fr=
om the tip of the git tree, if I should submit this another way, bug number=
etc.. let me know.
Paul
P.S. I couldn't find any requests like this in the bug tracker database.
--_000_92FCCC3A04F6DB48B59CE5FEC2612A6B1D1DBD09045SN2MPN205204_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Dimitri<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p> </o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I hope you don’t=
mind but I’m resending this to the develop list, this time with a sm=
aller zip file as the previous one bounced the email from the list an=
d I am unsure if the list received the message.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p> </o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The larger config.xml =
I removed, but outline the change needed here<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p> </o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">----------------------=
---------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"></docs><o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"> <=
;/option><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"> <=
;option type=3D'int' id=3D'LIMIT_WARNINGS' minval=3D'0' maxval=3D'10000' de=
fval=3D'0'><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"> &nbs=
p; <docs><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><![CDATA[<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The \c LIMIT_WARNINGS =
tag can be used to stop doxygen when a maximum number of warnings has been =
seen.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><br><o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">\b Tip: Turn warnings =
on while writing the documentation.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">]]><o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">----------------------=
---------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p> </o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Paul<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p> </o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:"=
;Tahoma","sans-serif"">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:"Tahoma","sans-serif""> Paul Hoa=
d
<br>
<b>Sent:</b> 03 December 2014 12:57<br>
<b>To:</b> '[email protected]'; '[email protected]'<br>
<b>Subject:</b> PATCH limit warnings from doxygen<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Dimitri<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">I recently posted a question on StackOverFlow regard=
ing being able to stop doxygen after it had seen a certain number of warnin=
gs, somewhat akin to the –ferror-limit=3DN option that certain compil=
ers have.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://stackoverflow.com/questions/271740=
31/possible-to-stop-doxygen-after-n-warnings">http://stackoverflow.com/ques=
tions/27174031/possible-to-stop-doxygen-after-n-warnings</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">I have a large code base, mostly un-doxygen’d,=
I have a nightly build that runs doxygen but its produces thousands of war=
nings. I know getting full coverage is going to require a gradual continuou=
s improvement approach which leads to a
mindset change of the individual teams of developers.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">So to tackle this I have added doxygen running on th=
e current source subdirectory as “PreBuild Event” in Visual Stu=
dio project files, I don’t want to use the temporary documentation it=
generates (that will come from the full tree nightly
build), but I want to see the warnings, I format the warnings with<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">WARN_FORMAT  =
; =3D "$file($line): $text"<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Which this means that while the code is compiling, t=
his allows the developer to go back in an<span style=3D"color:#1F497D">d</s=
pan> double click the warning<span style=3D"color:#1F497D">s</span> in the =
output window and be taken to the location
to fix those doxygen warnings (as they would any other warning), the probl=
em is that for many of the directories the number of warnings is huge (whic=
h are too daunting to fix in one go)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">I don’t want to do a full Doxygen scan everyti=
me (which is also why I only do it on the sub directory) because that will =
take too long and I don’t want all the warnings or the developer will=
simply treat it a noise, I just want them to
see a few and then stop.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">My idea is to be able to tell doxygen to document lo=
cally only a certain number of warnings and then stop, this means that ever=
y build the developer will see a few more warnings (but only a couple 5-10)=
and be driven to fix those, over
time the code will become documented and the developers will learn to docu=
ment as they go, also any new code (especially in previously doxygen clean =
areas) will immediately become a warning. Think of it a<span style=3D"color=
:#1F497D">s</span> “Continuous Incremental
Documentation”<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Given that I don’t think this is possible curr=
ently, I took it upon myself to try and learn how to do it, I am very new t=
o the doxygen source code, so I apologize in advance if I did it in the wro=
ng place.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">So the change to the doxygen source to implement som=
ething like this turned out to be fairly simple, with only having to add a =
new LIMIT_WARNINGS option to the config file, so I thought I would share th=
e code change, feel free to use or
discard as you see fit.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">So I’ve not contributed before, so I’m n=
ot 100% clear of the etiquette or who to send any diffs to, so I’ve i=
ncluded the changed files and the diff from the tip of the git tree, if I s=
hould submit this another way, bug number etc.. let
me know.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Paul<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">P.S. I couldn’t find any requests like this in=
the bug tracker database.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>
--_000_92FCCC3A04F6DB48B59CE5FEC2612A6B1D1DBD09045SN2MPN205204_--
--_004_92FCCC3A04F6DB48B59CE5FEC2612A6B1D1DBD09045SN2MPN205204_
Content-Type: application/x-zip-compressed; name="LIMIT_WARNING.zip"
Content-Description: LIMIT_WARNING.zip
Content-Disposition: attachment; filename="LIMIT_WARNING.zip"; size=3183;
creation-date="Wed, 03 Dec 2014 12:54:30 GMT";
modification-date="Mon, 05 Jan 2015 09:41:02 GMT"
Content-Transfer-Encoding: base64
UEsDBBQAAgAIAM1ig0WqFHZDXgMAAGUHAAASAAAATElNSVRfV0FSTklORy5kaWZmrVVtb9pIEP7u
XzFFbYHzCzYBN21C1DQvJ6SW6Bra+xAia+1dw0r22lovCbmq/72zaycYOJ3upEPIeHdmnnn2mZmF
8jQF111yBWRQyWSQFCLlS2+TZxDvbVhcULYBOgrjY5Z6Hh0zFo6PIfD9cDSyXNc9wLBs2z7E+fgR
3CA49p0QbPMbjAH3rqefr6LvV19vpzezaDq7voEJdJKMEamKIgPKqgTcNFewePNddCy4vz+zoP6c
DmiRVM3ydFCUihfizLLNsl6BeirZpMuF6gKnk+7n6ZfpPPrz/OtsOvv9tgs5Fw8km3R9fCUb84oH
83FJWdpYGkTErNPZp6/uLi7P5+d3aJivGCwS2MUFRZaQEAExg3XFKKgCKlWUQIvN05IJeFzhg+iU
PF/nINZ5zCQUKTwSKbhYVrAiFUajV4UPD3PGUvNYxDDn5QeYr6XYOhcakWcMHiVXuAMKWSHZdc6E
IloHRNDC2bvC2bvCwaFwMdagVk6fLZpeR99mlzcX375czeZXl1uVgu62Kk1RtirR/XbLWVWRJfOS
smz6pLXTNNwoGIfvhr7nvffZUUyHhw3Xjtl2XHtXt9ww1A2Hz3fYbRaWAfVI4I+LWyW1UsValWt1
XcicqJMXM7ZtpSBZEQm/NSpHlZK6NZvlB+j8vTuTspDPzmZhXO3GFTtRlzt6qd0EfAQaDFp2basZ
3UjK5AlaIUDH1ynW2HmdcYFPxTZKx8E/fNA61HHa9zlOY/yLuCMdt83UxJkZHgdmhMdD51gPcEP8
oeAUUsPaHK7XFsUQ10cziG2LBu9bYO3A0OIQAkfKgQNMeAHdsZWSpXyz558rBx5IlHHcInJZYdof
egRaymc8xyadwIW5tqIlU1Ohep3d6e70sZy623kKvVdb1084Kz2k2e+DZAoH1BSuKbSZJ6C8InHG
qI6uuems8Tq95X8xzDvy34e6HaDmrMW5a6z3J7X64ZFRPwyd4Ghf/v9DN538oRIlTodKe5qBnTnP
FF18NToa/QzRNkc3uJ90F37XGNq9YHKadKbeJ1r29hTYtpbU1tta1LoMb9/u+JxNzHb/R31tpQ3D
SuGISGevRvoufUOxDiRZ4f3LNvW9iP8q2ZO3EB2njVzzAePVC+rVT0t/rVrX/9DPRh3P8/rWL1BL
AwQUAAIACAB1YoNFrUgTdeEHAADCGQAACwAAAG1lc3NhZ2UuY3BwvRhpU9tG9Lt+xauaNFIRxiRp
OsGBTsqRMkMgAdJ+KB2PLK3snUi7rnZlcDP5731vtbp8QJweHg7r7bvv1c73/+rHAfqBQzmd53w8
0eAd+rD78uWP20/7u89hNIcjnnGdc5iFAn5hTEWTniV6x/KMK8WlAC2hUCyACPkEkMmYJ/g/FDHE
XCH1qNAM9IQrUDLRt2HOzCHXihjFMioyJnSoiVchYpYjMhKgAAUyMQ9vzj/AGyZYHqbwrhilPIIz
HjGhGCDbCcvZaE7MxnkoNIt7cC4hZ9OcqYqzApKbhTEKH8lCG7aq4Doc8ZTreSmppSOxS2SOqs5h
WuRTqVgPTjXJm+ZyxmMWgxsqfHbhlusJ8WR3JBK1zoFn05QjCrIinebkN7hi7CFzSGQmUdWY6ZCn
qvL3kXWTkR4XEbKm+Mi7+ZgJYxs6js/Q1hmDW5l/VCUA8ZJcZiSW2HAxRT0xXOh/QUCeW4bkpAFB
5oabkBrCJGGRLiUZ36SlklanHcf5losoLdCnr5SOuexNDlqgP+NQM80z1gG7kRQJH/cmbgtWaJ52
ITEbFQtIcWlsFziVOYYwZV1owlMWs6QLzDA04dhgOoqyIoL3h1eYoGIMGD10zInMs1APqlPUVGmI
JmEO32McBSIOMaFhH1z7uAfuSmyW5zKvcM1DG5MLDaLIhpaJQqT+wNnZaR3TUanNRY5xHMDODuwi
3iOyLHiUcoF/NbvTSAb3fPD0KZERakVGLB4me0ZkjZwvJXveKNnIfJjsh0bJxsKHyV40SjYy6+ie
nJ4dl5E7wUNExSTFYAwcZyY5FQDXv5UhKF3t+c4nI5MiQPzeSYrNoUnY4ZjpMlk897fXl+fDk4vL
t6+vXb+XcBF7rlHA9Qc1A1JrIwZE0GZAtmzEgAhKBoYH/iqsDmy0jDqpAOxh3HRZT1PLNHX+AqJQ
MeUbioWsQ8m7Vp0EPOuQg8qu776rfHRgNS2ZfLJhIxqLWyOQTuty8VMd7mU1ng7s4Wf7n6XYK1ck
xLqMvY/5sy7z8q8R0DL71bLZrzYze01R3KfZ86/UbJW/F8qqErss9IfBorDGr60iu5/JizaTdnPF
s9pgVYyU5hrXA69V6quhHTgsdIYH6iPoottSDdzHyu2cLCDaglrE62DZqkWcuMHxt57ciCfYZkxK
4gdXkTSMmPf+ko2P76aee3Nj24Vh7vfuxSzL+kswyw5ilPG3asxamYU4POA1Q0J59s0axLOLN9Rh
USmujrOpnnu+71BS1ClRdt1qRA8TOWXCe4hb4N6ScEoeK7/iZdJ5Kqk3ck1rp5IZw8UE5/csTHkc
wIhFIS43Rrrno49wBzOtj+tVmlXzgGR9duxYyNTYa8/yJNMB9Ho9Gg5LDvlZytRz3384PUaPNdYT
1hFtMHt7XJ2k4fiK6QpwjRuRQa2QATcwtCnx3Me9ZwkoFuGyEHheLHE1ZL7d8fb28kLQrCL6HkvD
KS5x6PGd3X6/3+sbj5U+A/TGMMXVGxv8WA0qCA7FXHsECgBtsgSzxApHX2B+mKPAEPo1JcPpUkOM
p+yANf5KTD6ZZabrN+oV1SAM2ieU0KU36/2LkK+owDEq9H1/vw8/gfuqEB+FvBUHLuwZ+KBNRIwN
0aD52lNMnxeZacF+B5ukViLoe+dwxnK6y5TcnGbgmZTDOFcI5TJNJyDCjNUBH2EeQJiN+Lj0GiXY
EUvQC/E+TWf77NXBNIv4ObI44pEOjK8MufW6kR93s6StI7kp3j5AzX4toV4rAT6Xpd80TLz35B8R
jxb5MNIFXjuwYAqm2i7AvL9Gt1CDXm7Eq5rzytbstPtyp2V3Z3W7FwULZ1WDrpOic+530asuXYfX
WYNateo6VZwVaO4j62U3aLvbWdXYTeFgj1FFqo0Dy/sFHia3OS5dnvVoD+9BoecHu0EFSJkY6wmC
6s42WKyqWC5XlA7HASyVWL1sds/wJprwuwV8qu12cyirsHXvSOnC35kNp0J77tnp29PrIfXp0/M3
V6tng2mFqKJPfVcXuTCXFnvHAT2fMnofQIMgRuJSLRI5KpIr/he14+f9ly/6lMZGWwro7/bwD1OT
pN9+vyrP0sCm5/6J1y0RTeee2Xes+ZbeFke6jzjo/Iq2mjIzJWwXJNqtNKiU2k4XG2Jbq+3dP/af
3PSfELzdBU1YTERMp6Pj9nVvawvd51SbIvkbN7c2wsG+AfulXa0GjcMqWIgFvbd4HKPHw2iCN3V2
x00usjBP570bTOM2Y+sGQvJ2m25uEm6D/t2diIvDZs2oqRLarbMogDJ/y9xtXbAXfd4ZQVBrjOAN
lV5O/a/Wqu22oaK3PWzj6bdyl2iK7IvqaHXeVU3da+nvwxbYfOwoX4hYRv9b5IenJ8MP50cXhx/e
Hp9fHx99ZRY4VLYtI9CEoXnP8r8agmYMjy8vLy6/3opOIFDD2PvHatYrXTVdAvDWJQTRVPPpwYJD
B//H2tXvzTbWzTBN2Z1H4Y5HOCjNSsaEZnl3CCIS7V3Lk5SgpSmdV3nEYajNYuSaB1TUHazDGhYR
IR43iFWhG5RmXHX44orIFfZvd9A9s9xO2sefK45oZffG0RhRriuLk2N7+7ECNJ9HuACGIkznf7F8
DxDoJdJ88Wli1NIDqH1Vs7YKpoptKmQ163oGW5brrbHXJyOuukudsbugTzfjTcxCp36RZZsLXCum
nrV/A1BLAQIUABQAAgAIAM1ig0WqFHZDXgMAAGUHAAASACQAAAAAAAEAIAAAAAAAAABMSU1JVF9X
QVJOSU5HLmRpZmYKACAAAAAAAAEAGABw/yzL8w7QAXD/LMvzDtABcC/HsPMO0AFQSwECFAAUAAIA
CAB1YoNFrUgTdeEHAADCGQAACwAkAAAAAAABACAAAACOAwAAbWVzc2FnZS5jcHAKACAAAAAAAAEA
GAAg73Vq8w7QAXD+9EXzDtABcP70RfMO0AFQSwUGAAAAAAIAAgDBAAAAmAsAAAAA
--_004_92FCCC3A04F6DB48B59CE5FEC2612A6B1D1DBD09045SN2MPN205204_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
--_004_92FCCC3A04F6DB48B59CE5FEC2612A6B1D1DBD09045SN2MPN205204_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Doxygen-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/doxygen-develop
--_004_92FCCC3A04F6DB48B59CE5FEC2612A6B1D1DBD09045SN2MPN205204_--