wrote: > Quoth Liane Praza on Thu, Oct 09, 2008 at 08:49:01PM -0700: > Quoth Liane Praza on Fri, Oct 10, 2008 at 09:31:11AM -0700: >>>>>> lib/libscf/common/scf_tmpl.c >>>>>> 3479: Why isn't this SCF_ERROR_TEMPLATE_INVALID? >>>>> Because it's defined not to be. Seemed like the most flexible >>>>> definition and is carried throughout its companion functions in the >>>>> manpage and the function comments. >>>> Ok, maybe I don't understand. Is there a way to create a property >>>> template through the manifest which does not have an >>>> SCF_PROPERTY_TM_TYPE property? >>> Sorry, thought I was looking at pg_type. I'll fix. >> Wait, no I won't. (Thanks to Antonello for noticing it's >> inappropriate.) The property type is absolutely not required in the >> prop pattern definition. That's why it's NOT_FOUND, which was my >> original point. > > Ok, sorry, I asked the wrong question. I should have asked "Is there > a way to create a property template through the manifest which has an > SCF_PROPERTY_TM_TYPE with a single empty value?" And then I think the > same decision process applies as for line 3972 above. David, you get an SCF_PROPERTY_TM_TYPE if the manifest has <prop_pattern> with no type attribute.
The second case of SCF_ERROR_NOT_FOUND would occur only if the type was manually deleted, which may not constitute an invalid template. If a property template exists and it has no type or type is an empty string, it means that property is wildcarded and can be of any type. Can you think of a case where this would be confusing? Antonello
