Lets start then

 Hi all,
 I guess we are properly set now. Without wasting much
time we should crack down, one by one, all the issues.

1. The first priority will to desing the system i.e
the interface, etc. I feel a single structure should
tell everything about the state of the codec. If we
have too many structures for each entity, no doubt it
will be modular, but we may have to pass many
strutures as arguments to functions. If we have a
single structure we can pass a pointer to it. We can
then access anything from it.

2. Regarding debugging we cannot go for #define DEBUG
sort of things.We can save a lot of time in
compilation if have a command line switch itself. we
can have wrapper functions which will print out
necessary information as dictated by cmd line args.

3. If we print debugging information in a standard
fashion(both at encoder and decoder) we can do
bitcompare on the printed matter. This way it will be
easy to debug.

4. Instead of everybody working on the same module we
can divide it based on our comfortable level with the
module. We can discuss about the progress of the
modules once in a while.

What does the group has to say about this.

Gopal

________________________________________________________________________
Send free SMS using the Yahoo! Messenger. Go to http://in.mobile.yahoo.com/new/pc/


-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1