Re: [dylan] Comments wanted: moving format-to-string, renaming simple-io

--===============2113950936==
Content-Type: multipart/alternative; boundary=f46d044402f454386704f98e96aa

--f46d044402f454386704f98e96aa
Content-Type: text/plain; charset=UTF-8

I've submitted the first step as a pull request:

    https://github.com/dylan-lang/opendylan/pull/752

Subsequent steps will have to happen after a release to keep bootstrapping
nice and clean.

 - Bruce



On Sat, Apr 26, 2014 at 5:03 PM, Bruce Mitchener
<[email protected]>wrote:

> Hello all,
>
> There is an annoyance when using both 'common-dylan' and 'format' (from
> io):
>
>     use common-dylan, exclude: { format-to-string };
>     use format;
>
> In the old functional-dylan library, there was a key difference between it
> and common-dylan.
>
> They had a simple-format module, which exported format-to-string and
> format-out and didn't export format-to-string from functional-extensions.
>
> In common-dylan, there is a simple-io module which exports format-out, but
> format-to-string is exported from functional-extensions.
>
> I'd like to suggest that we:
>
>
>    - Rename simple-io to simple-format
>    - Stop exporting format-to-string from common-extensions
>    - Start exporting format-to-string from simple-format
>
>
> Thoughts?  Should this get a DEP?
>
>  - Bruce
>
>

--f46d044402f454386704f98e96aa
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;ve submitted the first step as a pull request:<div><=
br></div><div>=C2=A0 =C2=A0 <a href=3D"https://github.com/dylan-lang/opendy=
lan/pull/752">https://github.com/dylan-lang/opendylan/pull/752</a><br></div=
><div><br></div>
<div>Subsequent steps will have to happen after a release to keep bootstrap=
ping nice and clean.</div><div><br></div><div>=C2=A0- Bruce</div><div><br><=
/div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On=
 Sat, Apr 26, 2014 at 5:03 PM, Bruce Mitchener <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:[email protected]" target=3D"_blank">bruce.mitchener@gm=
ail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Hello all,</div><div><=
br></div><div>There is an annoyance when using both &#39;common-dylan&#39; =
and &#39;format&#39; (from io):</div>
<div><br></div><div><div>=C2=A0 =C2=A0 use common-dylan, exclude: { format-=
to-string };</div>
<div>=C2=A0 =C2=A0 use format;<br></div></div><div><br></div>In the old fun=
ctional-dylan library, there was a key difference between it and common-dyl=
an.<div><br></div><div>They had a simple-format module, which exported form=
at-to-string and format-out and didn&#39;t export format-to-string from fun=
ctional-extensions.</div>

<div><br></div><div>In common-dylan, there is a simple-io module which expo=
rts format-out, but format-to-string is exported from functional-extensions=
.</div><div><br></div><div>I&#39;d like to suggest that we:<br></div><div>

<br></div><div><ul><li>Rename simple-io to simple-format<br></li><li>Stop e=
xporting format-to-string from common-extensions<br></li><li>Start exportin=
g format-to-string from simple-format<br></li></ul></div><div><br></div>

<div>Thoughts? =C2=A0Should this get a DEP?</div><span class=3D"HOEnZb"><fo=
nt color=3D"#888888"><div><br></div><div>=C2=A0- Bruce</div><div><br></div>=
</font></span></div>
</blockquote></div><br></div>

--f46d044402f454386704f98e96aa--

--===============2113950936==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
hackers mailing list
[email protected]
https://lists.opendylan.org/mailman/listinfo/hackers

--===============2113950936==--