<div dir="ltr"><br><br><div class="gmail_quote">On Fri, Aug 13, 2010 at 2:42 PM, Johan Tibell <span dir="ltr"><<a href="mailto:johan.tibell@gmail.com">johan.tibell@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote">Hi Erik,<div class="im"><br><br>On Fri, Aug 13, 2010 at 1:32 PM, Erik de Castro Lopo <span dir="ltr"><<a href="mailto:mle%2Bhs@mega-nerd.com" target="_blank">mle+hs@mega-nerd.com</a>></span> wrote:<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
Since the files are large I'm using ByteString, but that leads me<br>
to wonder what is the best way to handle clashes between Prelude<br>
functions like putStrLn and the ByteString versions?<br>
<br>
Anyone have any suggestions for doing this as neatly as possible?<br></blockquote></div></div><br>Use qualified imports, like so:<br><br>import qualified Data.ByteString as B<br> </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
main = B.putStrLn $ B.pack "test"<br>
<br></blockquote><div>If you want to pack a String into a ByteString, you'll need to import Data.ByteString.Char8 instead.</div><div><br></div><div>Michael </div></div></div>