question for the crowd: In writing the bitstream spec, I need to decide how to name various fields. I can go with names equivalent or very similar to the existing C code, or I can go with a similar set of labels that are more intuitive. Many of the C variables are named in cryptic or confusing ways. Presently, I'm changing the names to be more descriptive whenever it seems to make sense, but this may create confusion to someone looking at the spec and comparing it with the code. Thoughts? -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 2523 bytes Desc: winmail.dat Url : http://lists.xiph.org/pipermail/theora-dev/attachments/20030613/c19987f7/winmail-0001.bin
Imo you should change the names to make them more descriptive, and we can always change the variables names later to match the spec. Regards, Mauricio <p>>Presently, I'm changing the names to be more descriptive whenever it seems to make sense, but this may create confusion to someone >looking at the spec and comparing it with the code.>Thoughts?--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'theora-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.