<div class="gmail_quote">On Thu, Mar 26, 2009 at 10:23 PM, Robert Dailey <span dir="ltr"><<a href="mailto:rcdailey@gmail.com">rcdailey@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>I'm assuming that the macro in question will automatically mark all cache variables as advanced. Is this the case?</div><div><br></div><div>@Mike Jackson</div><div>Thank you for this info. I forgot about that function.</div>
<div><br></div><div>There seems to be an inconsistency in naming convention. For example, the set() function uses the term INTERNAL to represent a "hidden" cache variable. However, the function mark_as_advanced() is using the term "advanced". What I would like to see is one of the following pairs:</div>
<div><br></div><div>set( CACHE ADVANCED )</div><div>mark_as_advanced()</div><div><br></div><div> - OR -</div><div><br></div><div>set( CACHE INTERNAL )</div><div>mark_as_internal()</div><div><br></div><div>Does this make sense, or am I misunderstanding the difference between the two?</div>
</blockquote><div><br>You can consider INTERNAL "super advanced". It won't get shown in the cache editor at all. I think if you want an internal cache variable it probably should be created as an INTERNAL. In general you probably want to avoid using INTERNAL unless you really need it. Think of INTERNAL as a friendlier way to use set(...FORCE CACHE). Basically you're setting a cache variable you want to be persistent, but you don't want to confuse the user into thinking they have a choice in changing it.<br>
<br>Marking a variable as advanced is more of a discretionary thing. Generally when writing a find module a good rule of thumb is do not mark_as_advanced() by default. Generally, leave the user calling find_package() to do this and assume they care about the location of the library.<br>
</div></div><br>HTH<br><br>-- <br>Philip Lowman<br>