From: Avdi Grimm <groups@...>
Date: 2012-09-13T20:37:39+09:00
Subject: Re: Pathname#to_str withdrawn in 1.9?

--bcaec501c572f78c3904c993bbae
Content-Type: text/plain; charset=ISO-8859-1

I'd hazard a guess that the reasoning is because the '+' behavior was
confusing and potentially surprising. Pathname defines '+' as a filename
join, so Pathname('/foo') + Pathname('bar') == Pathname('/foo/bar'). But
'/foo' + Pathname('bar') == '/foobar'. This is surprising and bug-prone if
you have code that mixes pathnames and strings.

I'd recommend sticking to interpolation for pathname/string concatenation;
then it doesn't matter which object is what.
On Sep 12, 2012 11:06 PM, "Jonathan Tran" <lists@ruby-forum.com> wrote:

> It's definitely a judgment call. Not sure if this helps you, but I think
> most people use string interpolation, which calls #to_s implicitly. So I
> think this would work just fine in 1.9:
>
> require "pathname"
> f = Pathname("howdy")
> p "well #{f}"
>
> > The use cases are like this:
> >
> > require "pathname"
> > f = Pathname("howdy")
> > p ("well " + f)
> >
> > Under 1.8.7 that's "well howdy". Under 1.9.3 it's an error, "can't
> > convert Pathname into String." One wants to say: "Sure you can, just
> > call to_s like you used to!"
> >
> > It's the breakage I don't understand. Why do our Benevolent Masters
> > think this is just okay? I'll never find all the code where I'm doing
> > this sort of thing... m.
>
> --
> Posted via http://www.ruby-forum.com/.
>
>

--bcaec501c572f78c3904c993bbae
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p>I&#39;d hazard a guess that the reasoning is because the &#39;+&#39; beh=
avior was confusing and potentially surprising. Pathname defines &#39;+&#39=
; as a filename join, so Pathname(&#39;/foo&#39;) + Pathname(&#39;bar&#39;)=
 =3D=3D Pathname(&#39;/foo/bar&#39;). But &#39;/foo&#39; + Pathname(&#39;ba=
r&#39;) =3D=3D &#39;/foobar&#39;. This is surprising and bug-prone if you h=
ave code that mixes pathnames and strings. </p>

<p>I&#39;d recommend sticking to interpolation for pathname/string concaten=
ation; then it doesn&#39;t matter which object is what. </p>
<div class=3D"gmail_quote">On Sep 12, 2012 11:06 PM, &quot;Jonathan Tran&qu=
ot; &lt;<a href=3D"mailto:lists@ruby-forum.com">lists@ruby-forum.com</a>&gt=
; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It&#39;s definitely a judgment call. Not sure if this helps you, but I thin=
k<br>
most people use string interpolation, which calls #to_s implicitly. So I<br=
>
think this would work just fine in 1.9:<br>
<br>
require &quot;pathname&quot;<br>
f =3D Pathname(&quot;howdy&quot;)<br>
p &quot;well #{f}&quot;<br>
<br>
&gt; The use cases are like this:<br>
&gt;<br>
&gt; require &quot;pathname&quot;<br>
&gt; f =3D Pathname(&quot;howdy&quot;)<br>
&gt; p (&quot;well &quot; + f)<br>
&gt;<br>
&gt; Under 1.8.7 that&#39;s &quot;well howdy&quot;. Under 1.9.3 it&#39;s an=
 error, &quot;can&#39;t<br>
&gt; convert Pathname into String.&quot; One wants to say: &quot;Sure you c=
an, just<br>
&gt; call to_s like you used to!&quot;<br>
&gt;<br>
&gt; It&#39;s the breakage I don&#39;t understand. Why do our Benevolent Ma=
sters<br>
&gt; think this is just okay? I&#39;ll never find all the code where I&#39;=
m doing<br>
&gt; this sort of thing... m.<br>
<br>
--<br>
Posted via <a href=3D"http://www.ruby-forum.com/" target=3D"_blank">http://=
www.ruby-forum.com/</a>.<br>
<br>
</blockquote></div>

--bcaec501c572f78c3904c993bbae--