This is a multi-part message in MIME format.
------------7NhE3WuB9OnU6N9D2A0R5Y7
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C56DB4.C0495760"
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C56DB4.C0495760
Content-Type: text/plain; charset="iso-8859-1"
> Ah, that makes sense, in a way. I thought that "use" would
> be handled in
> the same way as the other properties at read time, and then
> the last value
> read would prevail, and then in a subsequent pass the "use"
> clauses would
> be expanded.
In the current code, it is done this way. Any 'use' directive overwrites the
previous one without being interpreted.
> if I understand well, "use" is handled specially at read
> time, right ?
No. Another reason why it cannot be handled at read time is that the current
syntax allows to "use" a template even if it is defined later in the same
file or in another.
One way to allow multiple template uses in an object could be to replace the
'template' field in xodtemplate objects by a template linked list and modify
the code in the xodtemplate_resolve_() functions to apply missing
properties from this template list. But, before doing that, we should extend
the template syntax to include more template combination options.
------_=_NextPart_001_01C56DB4.C0495760
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: Quoted-Printable
RE : [Nagios-devel] R=E9f. : Nagios-devel digest, Vol 1 #833 - 11 ms=
gs
> Ah, that makes sense, in a way. I thought that=
"use" would
> be handled in
> the same way as the other properties at read time, =
and then
> the last value
> read would prevail, and then in a subsequent pass t=
he "use"
> clauses would
> be expanded.
In the current code, it is done this way. Any 'use' direc=
tive overwrites the previous one without being interpreted.
> if I understand well, "use" is handled spe=
cially at read
> time, right ?
No. Another reason why it cannot be handled at read time =
is that the current syntax allows to "use" a template even if it =
is defined later in the same file or in another.
One way to allow multiple template uses in an object coul=
d be to replace the 'template' field in xodtemplate objects by a template l=
inked list and modify the code in the xodtemplate_resolve_<object>() =
functions to apply missing properties from this template list. But, before =
doing that, we should extend the template syntax to include more template c=
ombination options.
------_=_NextPart_001_01C56DB4.C0495760--
------------7NhE3WuB9OnU6N9D2A0R5Y7
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: Quoted-Printable
Ce message et ses pi=E8ces jointes (le "message") est destin=E9 =E0 l'usage=
=20
exclusif de son destinataire. =20
Si vous recevez ce message par erreur, merci d'en aviser imm=E9diatement =
l'exp=E9diteur et de le d=E9truire ensuite. Le pr=E9sent message pouvant =
=20
=EAtre alt=E9r=E9 =E0 notre insu, CALYON Corporate and Investment Bank =
=20
ne peut pas =EAtre engag=E9 par son contenu. Tous droits r=E9serv=E9s.=20
=20
This message and/or any attachments (the "message") is intended for =20
the sole use of its addressee. =20
If you are
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]