Re: [Nagios-devel] Nagios headers fails to compile in C++

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

Re: [Nagios-devel] Nagios headers fails to compile in C++

Post by Guest »

On Wed, Dec 15, 2010 at 5:24 PM, Glenn Herteg wrote:
> =C2=A0> It can't go in before 3.3 at the earliest. Otherwise I think it's=
a

Do you have any ETA about the release date of the 3.3 series ?

> =C2=A0> pretty good idea to either stay away from C++ reserved words enti=
rely
> =C2=A0> or declare plain C as the only valid language for NEB modules.
>

I definitely vote for no C++ keywords ;-) There is not much than C and
they're not that obvious and/or widely used.

> I don't get it. =C2=A0Since when are "command" and "contact" reserved wor=
ds
> in C++?
>

They're not. They're types defined in Nagios headers.

> I suspect a conflict not with the C++ language, but with something else
> in the OP's compilation environment.
>
> While "command" -> "cmd" is a common substitution in programs, I strongly
> dislike the "contact" -> "cntct" transformation. =C2=A0It's far less read=
able.
> Vowels are in the language for a reason.
>

Vowels are certainly useful but the problem is that 'contact' is also
a type. And as a matter of fact, the 'cntct' substitution is already
used thorough the code.

--=20
Matthieu KERMAGORET | D=C3=A9veloppeur

[email protected]

MERETHIS est =C3=A9diteur du logiciel Centreon.





This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Locked