Re: Re: wish: <tmpl_dump>

On Mon, 8 Aug 2005, Mark Stosberg wrote:

> Interesting. I hadn't heard of that technique being used before. I do
> recall that this feature could be accomplished somewhat automatically if
> code refs were used for values-- the code refs would only be executed if
> they were used. I have rarely needed that myself. 

For better or worse code-refs don't work for loops.  I'll fix that
someday!  Also, setting up a code-ref takes time that query() can save
you in many cases.

> > Heh.  Human-friendly YAML, huh?  
> 
> Yes. It's the first bullet point on the YAML website: 
> 
>  "YAML documents are very readable by humans."

I happen to disagree.  YAML is more readable than a lot of
serialization formats (probably all), but that doesn't make it fit for
documentation!  I'd call it "mostly readable by humans" I think.

> > I'm fresh out of time to look at it more closely but I think you're on
> > the right track.  I'm not completely convinced it belongs in-core yet,
> 
> There would be some immediate benefits. I believe being in-core would
> mean my "Dot" plugin could be used with HTML::Template::Set immediately,
> for those who cared to use both together. In the ::Pluggable sub-class, 
> ::Set has to be be re-written as a plugin to cooperate. 

I guess that's cool.  It doesn't exactly compel me to action though.
I tend to think of ::Set as an abomination better avoided than
supported!

> > if only because that would put you at the mercy of my absurdly slow
> > release schedule...
> 
> I'm really hoping the simple bug report for removing a hardcoded package
> name can be released soon, because even as a ::Pluggable sub-class, we
> depend on that patch. 

Yeah, I like that one.  Since you've put it in RT I can virtually
guarantee that it'll be in the next release.  It's hard to forget
things in RT.  I'll try to grab some time to make a release soon.

> I'm also help to with release engineering. For example, I could prepare
> things in CVS and you could refine them for release, or basically
> "bless" something if you liked it. 

Hmmmm.  Maybe.  You've been somewhat, how should I put it... hard to
persuade.  Here's how I'd like to proceed: you keep working on the
pluggable magic in a sub-class.  Keep me informed about stuff that
absolutely has to be fixed in-core and I'll try to get the fixes out
ASAP.  Some ways down the line, possibly as part of the fabled
HTML::Template 3.0 project, I'll see about merging in your sub-class.

Sound workable?

-sam


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf