Planet SoC

Hmmm, this blog hasn’t been used so far as I intended. Time to recommit to writing in this now that I am back from my wonderful birthday trip!

After waiting and waiting, finally I got my card from Google! Yoohoo!

Thank you Google for the Childern’s Day gift! :p

BTW, an ad: help Firefox 3 to Set a Guinness World Record!

After waiting and waiting, finally I got my card from Google! Yoohoo!

Thank you Google for the Childern’s Day gift! :p

BTW, an ad: help Firefox 3 to Set a Guinness World Record!

Already at an impasse- despite my best attempts, my compiler/parser knowledge (and tool knowledge) is too rusty/unsubstantial to really get down to coding all of my goals for MS 1. I understand where everything is located in the SWIG code and the the process, but code-browsing and Internetting isn’t enough- which isn’t surprising. Time to read through part of the “Dragon Book”! Gotta get this stuff done now :)

Hopefully writing down my progress will hold me well to my path :)
My name is Cheryl Foil- I am currently a student at the College of William and Mary.
My project for SWIG is taking C/C++/Doxygen comments from C/C++ files and placing them into the class that the other language works with- in the appropriate documentation language.
IE- If I am working with an example.c, the generated example.java will have the comments of example.c in JavaDoc :)
The first few steps have been very intimidating- After setting everything up and checking I could compile/run it- I have been combing through the SWIG manuals/Developers resources as well as pawing through the SWIG code itself.

I’m so glad to see that my blog has been added to Planet Python/SoC! Thanks Titus Brown for doing so.

Just saying a hello to everybody, and happy coding! :)

There’s some useful technique for debugging Python extension module, gathered during these days work.

• Clewn is a way to combine VIM and GDB.
• Set break on PyErrFormat or PyErrSetString so you can trace a Python exception raised from the extension module
• Use ‘make EXTEA_CFLAGS=”-ggdb3 -O0”’ to compile Python so you can have debugging symbol in the compiled executable. (Thanks my mentor Richard told me that.)
  

There’s some useful technique for debugging Python extension module, gathered during these days work.

• Clewn is a way to combine VIM and GDB.
• Set break on PyErrFormat or PyErrSetString so you can trace a Python exception raised from the extension module
• Use ‘make EXTEA_CFLAGS=”-ggdb3 -O0”’ to compile Python so you can have debugging symbol in the compiled executable. (Thanks my mentor Richard told me that.)
  

You can see it here: http://bugs.python.org/issue2899

It is about a problem in SWIG’s test cases. It used string.find(s, ‘abc’) to test whether ‘abc’ is contained in s. However, I don’t know what it has been written in this way. Maybe for compatibility with older Python like 2.2, 2.3?

And a good news, after these day’s working, nearly all test cases passed! Currently only 2 cases related to PyFile and 2 cases related to exception are still failed. I’ll continue to work on them.

Another good news is I have received my book from Google yesterday. A really beautiful book! :)

You can see it here: http://bugs.python.org/issue2899

It is about a problem in SWIG’s test cases. It used string.find(s, ‘abc’) to test whether ‘abc’ is contained in s. However, I don’t know what it has been written in this way. Maybe for compatibility with older Python like 2.2, 2.3?

And a good news, after these day’s working, nearly all test cases passed! Currently only 2 cases related to PyFile and 2 cases related to exception are still failed. I’ll continue to work on them.

Another good news is I have received my book from Google yesterday. A really beautiful book! :)