On Wed, Mar 12, 2014 at 08:15:11AM +0100, Niels Möller wrote: > When working with other specifications, I have tried to use variable > names matching names used in the specification. But with dca, that would > get a bit too ugly (the spec is written as some kind of pseudocode, with > hungarian naming, camelCase, "m_"-prefixes on some names, etc). > > So I try to come up with names that make sense to me. But then it's not > always obvious how variables in the implementation corresonds to the > spec/pseudocode. > > Any sugggestion on convention? I think it would make somse sense to add > a comment to each variable (local or in the state structs) spelling out > the corresponding name used in the spec. That would make it easier to > map variables in the code to the processing as described in the spec.
I'd suggest using lowercase without Hungarian, e.g. bUseSegStateCodeParm -> use_seg_state_code_parm _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
