I'm not actively involved in this project, but I'd like to share my own
perspective on general principles, which is that names (of anything)
should only describe, they should not carry metadata. People should
generally not change their names due to personal transitions,
municipalities should
Hi,
https://wiki.openoffice.org/wiki/Writer/Code_Conventions
has some info on this, more or less confirming what has been stated in
this thread already.
Regards,
Miklos
On 26.02.2022 20:48, Luboš Luňák wrote:
On Saturday 26 of February 2022, Jan Rheinlc3a4nder wrote:
Hi,
is there somewhere a key to naming variables?
'm' is member, 'r' is reference, 'p' is pointer, 'x' is UNO reference, 'a' is
array (or string), 's' is string, 'e' is enum, 'n' is number,
On Saturday 26 of February 2022, Jan Rheinlc3a4nder wrote:
> Hi,
>
> is there somewhere a key to naming variables? For example, I see
>
> OUString msDocAccTitle
> DocumentType meDocType
> std::unique_ptr mpGrammarContact
> const OUString& rBuffer
> SmFormat maFormat
> OUString
Hi,
is there somewhere a key to naming variables? For example, I see
OUString msDocAccTitle
DocumentType meDocType
std::unique_ptr mpGrammarContact
const OUString& rBuffer
SmFormat maFormat
OUString maAccText
bool mbFormulaArranged
sal_uInt16
