Haskell Weekly News: February 06, 2006
Greetings, and thanks for reading issue 23 of HWN, a weekly newsletter
covering developments in the Haskell community. Each Monday, new
editions are posted to [1]the Haskell mailing list and to [2]The
Haskell Sequence. [3]RSS
On Mon, Feb 06, 2006 at 03:36:17PM +, Simon Marlow wrote:
> So I'm of the opinion that introducing an ADT for FilePaths is something
> that should wait until the I/O library is revised. In the meantime, we
> should include a String-based Data.FilePath library in Haskell'. It's
> not as ele
Hello Tomasz,
Monday, February 06, 2006, 8:29:32 PM, you wrote:
>> is it possible to implement unsafeInterleaveST?
TZ> I hope not. You surely shouldn't be able to implement this function
TZ> without unsafe* functions, because that would break ST's guarantees.
of course. i asked from language/li
Hello Aaron,
Monday, February 06, 2006, 9:46:56 PM, you wrote:
>> ps: the library also includes two more layers - binary I/O and
>> serialization - on top of Streams. now i'm hardly working on
>> documenting these modules
AD> Disclaimer: I haven't looked at the code yet.
AD> Having binary I/O o
On Mon, Feb 06, 2006 at 03:36:17PM +, Simon Marlow wrote:
> The reason we can't just go right ahead and do The Right Thing (i.e.
> introduce a new ADT for FilePaths) is because it touches so much other
> stuff, including stuff that also needs revising, so it doesn't feel
> right to just fix
Bulat Ziganshin writes:
> You can find further information about the library at the
> page http://haskell.org/haskellwiki/Library/Streams and
> download it as http://freearc.narod.ru/Streams.tar.gz
Is there any chance of running this code on a non-Windows
system? I tried to compile the example
On 2006-02-06, Bulat Ziganshin <[EMAIL PROTECTED]> wrote:
> Hello
>
> I have developed a new I/O library that IMHO is so sharp that it can
> eventually replace the current I/O facilities based on using Handles.
> The main advantage of the new library is its strong modular design
> using typeclasses
On Mon, Feb 06, 2006 at 06:31:17PM +0300, Bulat Ziganshin wrote:
> is it possible to implement unsafeInterleaveST?
I hope not. You surely shouldn't be able to implement this function
without unsafe* functions, because that would break ST's guarantees.
Hell, you would be able to return frozen ST co
Hello
I have developed a new I/O library that IMHO is so sharp that it can
eventually replace the current I/O facilities based on using Handles.
The main advantage of the new library is its strong modular design
using typeclasses. The library consists of small independent modules,
each implementin
Hello haskell,
is it possible to implement unsafeInterleaveST?
why i want it: i have the following definitions:
class (MonadHelper m) => Stream m h where
vGetContents :: h -> m String
-- default definition
vGetContents h = mUnsafeInterleaveIO $ do
eof <- vIs
On 2/6/06, Simon Marlow <[EMAIL PROTECTED]> wrote:
> Isaac Jones wrote:
>
> > Has anyone yet volunteered to do the hard work of defining an ADT and
> > made a proposal for how it should interact w/ the System.IO functions?
> >
> > I think that lacking a FilePath module is a serious problem that is
Isaac Jones wrote:
Has anyone yet volunteered to do the hard work of defining an ADT and
made a proposal for how it should interact w/ the System.IO functions?
I think that lacking a FilePath module is a serious problem that is
holding haskell back. Lots of languages use String for filepath, l
Before Christmas I invited people on this mailing list to complete a web
survey about the use of Haskell in higher education. Many have done
so--thank you very much! I received 126 responses from 89 universities,
accounting for 5-10,000 students taught using Haskell this academic
year. The surv
13 matches
Mail list logo
