From: The C. <the...@ji...> - 2012-08-29 12:05:28
|
I understand there's a 2012 GSoC project to update the 2008 work and perhaps merge this with the main trunk. I'm wondering (and I apologize if I shouldn't be asking this here) what the status of that work is. Thanks Jim Carroll |
From: Marko K. <mar...@is...> - 2012-08-30 06:26:58
|
Hi, Comment parsing is in much better state now, although still not perfect. I'm using it on my project and I plan to publish examples in a week or two. The biggest issue is parsing of comments, which is done with bison rules at the moment. The disadvantage of this approach is that it is close to impossible to cover all possible locations where comment can be placed, so SWIG reports syntax error on valid C/C++ code. However, if you have access to C/C++ sources, you can always move doxy comment to a place, where both Doxygen and SWIG are happy. Regarding merge to trunk, William should decide. Regards, Marko On 2012-08-29 2:05 PM, The Carrolls wrote: > I understand there's a 2012 GSoC project to update the 2008 work and > perhaps merge this with the main trunk. I'm wondering (and I apologize > if I shouldn't be asking this here) what the status of that work is. > > Thanks > Jim Carroll > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Swig-devel mailing list > Swi...@li... > https://lists.sourceforge.net/lists/listinfo/swig-devel > > -- Marko Klopcic, +386 1 5680695, www.asystelectronic.si Asyst electronic d.o.o. / iSYSTEM AG Brodisce 18, SI-1236 Trzin, SLOVENIA |
From: The C. <the...@ji...> - 2012-08-30 17:21:36
|
Thanks for the info. We're going to be using SWIG inside of XBMC (http://xbmc.org/) I was really hoping not to require doxygen as another build dependency - or at least have a concrete plan for moving off of it in the future. If it works parsing standard doxygen (/** ... */) comments into the parse tree then it gets my vote! ;-) If you're interested: project details: http://wiki.xbmc.org/index.php?title=Category:Codegeneration PR here: https://github.com/xbmc/xbmc/pull/901 ). Thanks again. Jim On 08/30/12 02:26, Marko Klopcic wrote: > Hi, > > Comment parsing is in much better state now, although still not perfect. > I'm using it on my project and I plan to publish examples in a week or two. > The biggest issue is parsing of comments, which is done with bison rules > at the moment. The disadvantage of this approach is that it is close > to impossible to cover all possible locations where comment can be placed, > so SWIG reports syntax error on valid C/C++ code. However, if you have > access to C/C++ sources, you can always move doxy comment to a place, where > both Doxygen and SWIG are happy. > Regarding merge to trunk, William should decide. > > Regards, > > Marko > > > On 2012-08-29 2:05 PM, The Carrolls wrote: >> I understand there's a 2012 GSoC project to update the 2008 work and >> perhaps merge this with the main trunk. I'm wondering (and I apologize >> if I shouldn't be asking this here) what the status of that work is. >> >> Thanks >> Jim Carroll >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Swig-devel mailing list >> Swi...@li... >> https://lists.sourceforge.net/lists/listinfo/swig-devel >> >> > > |
From: Marko K. <mar...@is...> - 2012-08-31 06:35:53
|
Hi, Just to prevent misunderstanding - SWIG is not replacement for Doxygen. It just copies code documentation from C/C++ code to the generated Java and Python code. It also translates Doxygen tags to the target language (javadoc) tags. You'll still need a tool (javadoc, doxygen, ...) to produce HTML documentation. Regards, Marko On 2012-08-30 7:21 PM, The Carrolls wrote: > Thanks for the info. > > We're going to be using SWIG inside of XBMC (http://xbmc.org/) I was > really hoping not to require doxygen as another build dependency - or at > least have a concrete plan for moving off of it in the future. > > If it works parsing standard doxygen (/** ... */) comments into the > parse tree then it gets my vote! ;-) > > If you're interested: > > project details: > http://wiki.xbmc.org/index.php?title=Category:Codegeneration > PR here: https://github.com/xbmc/xbmc/pull/901 ). > > Thanks again. > Jim > > On 08/30/12 02:26, Marko Klopcic wrote: >> Hi, >> >> Comment parsing is in much better state now, although still not perfect. >> I'm using it on my project and I plan to publish examples in a week or two. >> The biggest issue is parsing of comments, which is done with bison rules >> at the moment. The disadvantage of this approach is that it is close >> to impossible to cover all possible locations where comment can be placed, >> so SWIG reports syntax error on valid C/C++ code. However, if you have >> access to C/C++ sources, you can always move doxy comment to a place, where >> both Doxygen and SWIG are happy. >> Regarding merge to trunk, William should decide. >> >> Regards, >> >> Marko >> >> >> On 2012-08-29 2:05 PM, The Carrolls wrote: >>> I understand there's a 2012 GSoC project to update the 2008 work and >>> perhaps merge this with the main trunk. I'm wondering (and I apologize >>> if I shouldn't be asking this here) what the status of that work is. >>> >>> Thanks >>> Jim Carroll >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> Swig-devel mailing list >>> Swi...@li... >>> https://lists.sourceforge.net/lists/listinfo/swig-devel >>> >>> >> > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Swig-devel mailing list > Swi...@li... > https://lists.sourceforge.net/lists/listinfo/swig-devel > > -- Marko Klopcic, +386 1 5680695, www.asystelectronic.si Asyst electronic d.o.o. / iSYSTEM AG Brodisce 18, SI-1236 Trzin, SLOVENIA |
From: William S F. <ws...@fu...> - 2012-08-31 07:25:53
|
From what I understand of the XBMC approach, they are using SWIG -xml to get a dump of the parse tree and having the doxygen comments in the dumped xml will be extremely useful. Presumably they would write tools to process the doxygen comments in much the same way they replicate a lot of what SWIG does. With regard to merge to trunk, please follow the other "Doxygen queries" email thread. William On 31/08/12 07:35, Marko Klopcic wrote: > Hi, > > Just to prevent misunderstanding - SWIG is not replacement for Doxygen. > It just copies > code documentation from C/C++ code to the generated Java and Python > code. It also translates Doxygen tags to the target language (javadoc) tags. > You'll still need a tool (javadoc, doxygen, ...) to produce HTML > documentation. > > Regards, > > Marko > > On 2012-08-30 7:21 PM, The Carrolls wrote: >> Thanks for the info. >> >> We're going to be using SWIG inside of XBMC (http://xbmc.org/) I was >> really hoping not to require doxygen as another build dependency - or at >> least have a concrete plan for moving off of it in the future. >> >> If it works parsing standard doxygen (/** ... */) comments into the >> parse tree then it gets my vote! ;-) >> >> If you're interested: >> >> project details: >> http://wiki.xbmc.org/index.php?title=Category:Codegeneration >> PR here: https://github.com/xbmc/xbmc/pull/901 ). >> >> Thanks again. >> Jim >> >> On 08/30/12 02:26, Marko Klopcic wrote: >>> Hi, >>> >>> Comment parsing is in much better state now, although still not perfect. >>> I'm using it on my project and I plan to publish examples in a week or two. >>> The biggest issue is parsing of comments, which is done with bison rules >>> at the moment. The disadvantage of this approach is that it is close >>> to impossible to cover all possible locations where comment can be placed, >>> so SWIG reports syntax error on valid C/C++ code. However, if you have >>> access to C/C++ sources, you can always move doxy comment to a place, where >>> both Doxygen and SWIG are happy. >>> Regarding merge to trunk, William should decide. >>> >>> Regards, >>> >>> Marko >>> >>> >>> On 2012-08-29 2:05 PM, The Carrolls wrote: >>>> I understand there's a 2012 GSoC project to update the 2008 work and >>>> perhaps merge this with the main trunk. I'm wondering (and I apologize >>>> if I shouldn't be asking this here) what the status of that work is. >>>> >>>> Thanks >>>> Jim Carroll >>>> >>>> ------------------------------------------------------------------------------ >>>> Live Security Virtual Conference >>>> Exclusive live event will cover all the ways today's security and >>>> threat landscape has changed and how IT managers can respond. Discussions >>>> will include endpoint security, mobile security and the latest in malware >>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>> _______________________________________________ >>>> Swig-devel mailing list >>>> Swi...@li... >>>> https://lists.sourceforge.net/lists/listinfo/swig-devel >>>> >>>> >>> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Swig-devel mailing list >> Swi...@li... >> https://lists.sourceforge.net/lists/listinfo/swig-devel >> >> > > |
From: The C. <the...@ji...> - 2012-09-04 09:51:02
|
This is exactly right. Thanks for the note. On 08/31/12 03:25, William S Fulton wrote: > From what I understand of the XBMC approach, they are using SWIG -xml > to get a dump of the parse tree and having the doxygen comments in the > dumped xml will be extremely useful. Presumably they would write tools > to process the doxygen comments in much the same way they replicate a > lot of what SWIG does. > > With regard to merge to trunk, please follow the other "Doxygen queries" > email thread. > > William > > On 31/08/12 07:35, Marko Klopcic wrote: >> Hi, >> >> Just to prevent misunderstanding - SWIG is not replacement for Doxygen. >> It just copies >> code documentation from C/C++ code to the generated Java and Python >> code. It also translates Doxygen tags to the target language (javadoc) tags. >> You'll still need a tool (javadoc, doxygen, ...) to produce HTML >> documentation. >> >> Regards, >> >> Marko >> >> On 2012-08-30 7:21 PM, The Carrolls wrote: >>> Thanks for the info. >>> >>> We're going to be using SWIG inside of XBMC (http://xbmc.org/) I was >>> really hoping not to require doxygen as another build dependency - or at >>> least have a concrete plan for moving off of it in the future. >>> >>> If it works parsing standard doxygen (/** ... */) comments into the >>> parse tree then it gets my vote! ;-) >>> >>> If you're interested: >>> >>> project details: >>> http://wiki.xbmc.org/index.php?title=Category:Codegeneration >>> PR here: https://github.com/xbmc/xbmc/pull/901 ). >>> >>> Thanks again. >>> Jim >>> >>> On 08/30/12 02:26, Marko Klopcic wrote: >>>> Hi, >>>> >>>> Comment parsing is in much better state now, although still not perfect. >>>> I'm using it on my project and I plan to publish examples in a week or two. >>>> The biggest issue is parsing of comments, which is done with bison rules >>>> at the moment. The disadvantage of this approach is that it is close >>>> to impossible to cover all possible locations where comment can be placed, >>>> so SWIG reports syntax error on valid C/C++ code. However, if you have >>>> access to C/C++ sources, you can always move doxy comment to a place, where >>>> both Doxygen and SWIG are happy. >>>> Regarding merge to trunk, William should decide. >>>> >>>> Regards, >>>> >>>> Marko >>>> >>>> >>>> On 2012-08-29 2:05 PM, The Carrolls wrote: >>>>> I understand there's a 2012 GSoC project to update the 2008 work and >>>>> perhaps merge this with the main trunk. I'm wondering (and I apologize >>>>> if I shouldn't be asking this here) what the status of that work is. >>>>> >>>>> Thanks >>>>> Jim Carroll >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Live Security Virtual Conference >>>>> Exclusive live event will cover all the ways today's security and >>>>> threat landscape has changed and how IT managers can respond. Discussions >>>>> will include endpoint security, mobile security and the latest in malware >>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>> _______________________________________________ >>>>> Swig-devel mailing list >>>>> Swi...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/swig-devel >>>>> >>>>> >>>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> Swig-devel mailing list >>> Swi...@li... >>> https://lists.sourceforge.net/lists/listinfo/swig-devel >>> >>> >> >> > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Swig-devel mailing list > Swi...@li... > https://lists.sourceforge.net/lists/listinfo/swig-devel > |