Shubham,
>> - Aim for formal correctness regarding the coding style. E.g. indents
>> (anno.c line 78 or 1781 et seqq.), consistent number of line feeds
>> between the functions, no trailing spaces. When your patch is
>> formally correct I can check it in.
>
> Apologies for that! I'll do it as soon as possible.
I'm still waiting for your patch. Thursday is the last day where I
can review your code before the first evaluations, and patches usually
need some iteration loops before they can be accepted.
Your previous patches looked promising but where incomplete. I really
would like to see something compiling and working before I let you
pass. Regarding your development log this should be feasible. But,
don't wait until the last moment.
Regards,
Daniel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
