<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2012/12/27 David Precious <span dir="ltr"><<a href="mailto:davidp@preshweb.co.uk" target="_blank">davidp@preshweb.co.uk</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
</div>I'm not sure; a lot of existing plugins use dancer_version, and it's<br>
meaning is fairly clear.<br>
<br>
I think the pragmatic approach is to let them continue to do so, with a<br>
couple of tweaks:<br>
<br>
- dancer_version can strip /_\d+$/ so that dev releases don't cause<br>
issues<br>
- a special-case for D2 - e.g. return 2 if ($version >= 1.9) - if the<br>
code is calling dancer_version, it most likely wants to know the<br>
difference between D1 and D2, I can't see that it's likely to be<br>
used in many other ways, you'd tend to use $Dancer::VERSION for that.<br>
<br></blockquote><div><br></div><div style>Good point, I like that approach. Then we should remove api_version. I don't even know why it was introduced to be frank :)</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">
<br>
</div></div></blockquote></div><br></div></div>