Something to clarify how to use an slist (and ilist and rlist), from
other bundles would also be helpful, since they are apparently not
treated the same way as a string variable.
My understanding is that you can directly call
${bundle.string_variable} for strings, you can *not* directly
reference ${bundle.slist_variable}. This is very confusing.
And thanks, :)
On Thu, Sep 16, 2010 at 19:05, Daniel V. Klein <d...@lonewolf.com> wrote:
> Yes, I will make sure it is clearer... maybe not 72pt, though :-)
>
> On Sep 16, 2010, at 4:44 PM, Jesse Becker wrote:
>
>> Is there a way to have this Seva's comment below integrated into the
>> docs, preferably in 72pt type :-)
>>
>> Subtleties like this are nearly impossible to find in the current
>> reference manual.
>>
>>
>> On Thu, Sep 16, 2010 at 16:38, <no-re...@cfengine.com> wrote:
>>> Forum: Cfengine Help
>>> Subject: Re: Accessing variables declared within cf3 modules
>>> Author: Seva Gluschenko
>>> Link to topic: https://cfengine.com/forum/read.php?3,18279,18295#msg-18295
>>>
>>> mikec Wrote:
>>> -------------------------------------------------------
>>>> The manual *does* say that to access variables
>>>> that aren't in a global (common)
>>>> scope need to be qualified
>>>
>>> This statement is not quite true. Variables defined in common bundles don't
>>> become global and must be qualified outside the scope of the bundle
>>> anyway. Your link shows that explicitly. Only classes defined in common
>>> bundles become global.
>>>
>>> _______________________________________________
>>> Help-cfengine mailing list
>>> Help-cfengine@cfengine.org
>>> https://cfengine.org/mailman/listinfo/help-cfengine
>>>
>>
>>
>>
>> --
>> Jesse Becker
>> _______________________________________________
>> Help-cfengine mailing list
>> Help-cfengine@cfengine.org
>> https://cfengine.org/mailman/listinfo/help-cfengine
>
>
--
Jesse Becker
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
