Re: [C++] Coding convention for #ifndef in our includes

2006-08-24 Thread Jean-Sebastien Delfino
Pete Robbins wrote: I prefer the SCA style rather than the ones in SDO. The full path is better as well so #ifndef commonj_sdo_changeddataobjectlist_h is what I would use. However, I don't think this affects the readabillity of the code so I don't propose we change them all. We need to update

Re: [C++] Coding convention for #ifndef in our includes

2006-08-23 Thread Pete Robbins
I prefer the SCA style rather than the ones in SDO. The full path is better as well so #ifndef commonj_sdo_changeddataobjectlist_h is what I would use. However, I don't think this affects the readabillity of the code so I don't propose we change them all. We need to update the licence header in e

Re: [C++] Coding convention for #ifndef in our includes

2006-08-23 Thread haleh mahbod
Can you please update C++ development website to include conventions that are agreed to? On 8/23/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: I see two different coding conventions for the usual #ifndef/#define/#endif in our include files: #ifndef tuscany_sca_model_binding_h in tuscany

[C++] Coding convention for #ifndef in our includes

2006-08-23 Thread Jean-Sebastien Delfino
I see two different coding conventions for the usual #ifndef/#define/#endif in our include files: #ifndef tuscany_sca_model_binding_h in tuscany::sca::model::Binding.h #ifndef _CHANGEDDATAOBJECTLIST_H_ in commonj::sdo::ChangedDataObjectList.h Can we decide on a common convention? I have used bot