tag:blogger.com,1999:blog-1966164648581347177.post4740974550446920465..comments2024-02-27T00:13:27.308-08:00Comments on On the Bleeding Edge of Puppet: Class and Resource TypesHenrik Lindberghttp://www.blogger.com/profile/18131140901733897033noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1966164648581347177.post-35791205200159149852013-12-31T09:07:05.442-08:002013-12-31T09:07:05.442-08:00I am unsure about the exact types in the catalog, ...I am unsure about the exact types in the catalog, and which ones need a representation as a Type. There is work remaining in this area. And yes, there are plans to add type declarations in define and class parameter lists to get automatic type checking. Not sure that will make it into the future parser for 3.5, but should for 3.6. I would also like to add type/parameter declaration and checking to custom functions, also no time to do this for 3.5.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1966164648581347177.post-76127526319856773452013-12-30T11:02:49.458-08:002013-12-30T11:02:49.458-08:00Interesting and informative posts Henrik!
But I&#...Interesting and informative posts Henrik!<br /><br />But I'm wondering about two things. Isn't Schedule also a type represented in the catalog?<br />And are there any plans for allowing type expressions directly in class and define parameter lists? Just taking any type as input and then validating each of them later on seems a bit tedious.Erik Dalénhttps://www.blogger.com/profile/04850422349118133112noreply@blogger.com