Hello!
During the first part of GSoC program I:
1. Found, reducted (where it was possible) and patched all the duplications
which are contained in ONE (the same) file. For example, my very last
accepted patch. There're some patches which are similar to it. There're:
3534954, 3534955 and 3534956. Here's the first one:
http://sourceforge.net/tracker/?func=detail&aid=3534954&group_id=105292&atid=640804.
Please, check them, I need it to get commit access.
2. Found, reducted (where it was possible) and patched all (except one) the
duplications which are contained in different files, but in one directory.
Usually I added 2 new files - util.c and util.h, which contained the
duplicated code. I need to add some necessary comments to the new files.
Also I have a question about headers. I've read about their order in
HACKING file. But, for example, I have umod.c which has "include util.h"
and util.h has "include bu.h", "include bn.h" etc. So can I NOT include
bn.h, bu.h etc in umod.c, if they've already been in util.h?
3. Created some small manual pages for some programs in src/sig. Will
commit them after the getting commit access.
4. Found all the duplications which are contained in different directories
and have a full list of necessary reductions.I have a question here too.
Where shall I put the common code for such situations? For example,
there're lots of duplications and copy-pastes from src/libged to src/mged.
So Shall I create a new library or to leave the common code in one of these?
Hope, it was quite detailed report. I'm lookong forward tp checking my
patches.
Best, Ksenija
------------------------------------------------------------------------------
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/
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel