Planet SoC

Well, some victory!

Example.h:

The TOP of foo.java


/* This was generated from emitProxyClassDefAndCPPCasts() */
/**
* This is describing class foo
*
*/

public class Foo {


and finally-

}


Wish I still wasn’t so tired from being sick! But on the nice side, the Olympic opening ceremony was wonderful :) Couldn’t help but watch it!
Trying to finish what I had started on my laptop on my trip has been a little hairy- mostly I’ve been having to rewrite things to get them to actually work, but it’s given me some good opportunities to reconsider how much work I want the language modules to have to do (Which is, of course, as little as possible- and preferably in a manner that leaves all the modules I am not going to mess with untouched!)
With any luck though, my build tomorrow should be putting my javaDoc into the java proxy files. I still haven’t worked out my problem with implementing a %feature, but I decided It would probably be best to get it working end to end first- plus there is the option of simply adding in a new blob of doxygen with a structural command into the interface file itself. (Note to self: make sure to bring this up with Olly TOMORROW!)

First spam comment! How exciting. :p It’s on some post down below. Other than that, committing tomorrow instead . Oof, I feel behind! William’s post on the mailing list gave me a lot to chew on though, need to reply formally to both of my threads tomorrow ( _really_ tomorrow) as well. I also need to make sure to exist on the swig gsoc channel more- haven’t been holding to that.
Other than that- still need to figure out best way to deal with straight C/C++ comments.

Thunderstorms all morning + keeping watch over a very neurotic dog during said storms did not bode well for our heroine. However, tomorrow should be the update of a build with some fixes/extensions to the translator module as well as what I talked about yesterday implemented in SWIG. As well as (hopefully) a good plan for a few of the language modules. Should give me some good talking material :)
also, memo to self- need to still discuss how to appropriately put in a new command line option, or what, in order to make my module run. Seems like disabling the functionality would be as easy as just turning off parsing the tokens or placing them into the tree.

Ahhhh, I feel too tired to clearly articulate myself right now. I think I’m going to have to finish this tomorrow morning. I need to stop working/blogging so late- I’m really much more in my element in the morning… Like Cinderella’s coach, my brain turns into a pumpkin past midnight- which makes my time commitment from 7-11pm M T TH a little inconvenient ><
Plan details
Stage 1:

Picking up comments
in cscanner.c at case SWIG_TOKEN_COMMENT:
(around line 420 in my version)
3 types of tokens will be returned
-for standard doxygen blobs (aka /** or ///, //! etc) DOXYGENSTRING

-for post comments suchas /**< ///< etc (which are associated with the last thing encountered, see “Putting comments after members” at http://www.stack.nl/~dimitri/doxygen/docblocks.html for more info) DOXYGENPOSTCOMMENT

-for normal C/C++ comments CSTYLECOMMENT

Stage 2:
Attachment into the parse tree
in parser.y

General Doxygen Comments:

First, I have arrival Haikou tonight, and then have eaten some delicious. :)

Secondly, the GSoC payment has sent to my store value card right now! Hopefully every GSoCers have got it. :)

Spent today doing a few tweaks then more SWIG code review and a lot of reading through some documentation. Instead of my previous “beat SWIG with a stick until it does something” attempts, I’m going to lay out a very technical plan tomorrow. Running it by Olly and hopefully some other SWIG mentors should be a good way to ensure that its actually feasible- and it’s always good to make sure what I believe is the desired functionality… is actually the desired functionality ;) Would be very nice to set out with a good design. I also need to look up a bit more on some things like using error numbers and such so I can develop for SWIG properly.
I also need to figure out what modules are going to want the option to have doxygen, and how best to deal with that.

Well, finally I have came back to the earth!

After a super busy month, many things get done - the exams, TOEFL, GSoC midterm evaluation, rent room in Singapore, … Another good news is my GSoC project still on track! Though, well, I have a little trouble of implementing the Python buffer support - I havn’t a clear plan about what I am going to do…

Tonight I will go to Haikou, and then contiune my summer in this hot beatiful city. :)

(output from the latest build of mine)

---ORIGINAL DOXYGEN---
//! A normal member taking two arguments and returning an integer value. This is a very long description for the simple purpose of showing off formatting. Let's make it a bit longer just to be sure.
/*!
\param a an \b integer argument.
\return The test results
\param s a constant character pointer. Let's also make this a very long description!
\bug this command should, for now, be totally ignored
\author cheryl foil
\sa Test(), ~Test(), testMeToo() and publicVar()
*/


---RESULT IN JAVADOC---
/**
* A normal member taking two arguments and returning an integer value.
* This is a very long description for the simple purpose of showing
* off formatting. Let's make it a bit longer just to be sure.
*
* @author cheryl foil
* @param s a constant character pointer. Let's also make this a very
* long description!