Hi !
I got an "fatal error: GetMBlock:misaligned block returned" message wenn
executing my program.
Because I have no idea what that means,I decided to compile with profiling
optin.
(I youse a makefile as You describe it in the user - report.)
So I changed the HC_OPTS (to: -O -prof -auto-all
"Frank A. Christoph" wrote:
I have a humble wish for the Wish List.
I wish this function was in the Prelude or standard library:
concatSep :: [a] - [[a]] - [a]
with semantics
concatSep _ [] = []
concatSep _ [xs] = [xs]
concatSep sep (xs:xss) = xs ++ sep ++ concatSep sep xss
On Wed, 8 Sep 1999, S. Alexander Jacobson wrote:
Are we talking about documentation for the H98 libraries?
Are these libraries relevant? Don't MPTC, Existential Types, Restricted
Type Synonyms, Arrows, and an FFI substantial change the architecture,
interface, and implementation of the
Don't add more functions like concatSep to the standard library or prelude. Instead
document
what is there better. I found it far easier to find functions in the Standard ML Basis
library than in the Haskell standard. Here are some suggestions for what could be
done:
(1) document the IO
Michael Hobbs writes:
I have been "scratching a personal itch" lately and was wondering if
anyone else has the same itch. [...]
[...] it is not possible to create a list of values that may be of
different [Haskell] type, but all implement the same interface.
[...]
Hi.
Is it
Frank A. Christoph writes:
I have a humble wish for the Wish List.
I wish this function was in the Prelude or standard library:
concatSep :: [a] - [[a]] - [a]
with semantics
concatSep _ [] = []
concatSep _ [xs] = [xs]
concatSep sep (xs:xss) = xs ++ sep ++ concatSep sep
Wed, 8 Sep 1999 18:36:14 +0900, Frank A. Christoph [EMAIL PROTECTED] pisze:
concatSep :: [a] - [[a]] - [a]
with semantics
concatSep _ [] = []
concatSep _ [xs] = [xs]
concatSep sep (xs:xss) = xs ++ sep ++ concatSep sep xss
It is already defined: concat . List.intersperse
--
On Wed, 8 Sep 1999, Mark P Jones wrote:
We've been working on this, and the next release of Hugs is dropping
the Artistic license in favor of a more liberal license; essentially
the same license that is being used for GHC (in part to make the
integration of Hugs and GHC that little bit
If you have some type of generic programming interface, then unzip changes
too. Unzip gets generalized from working only with lists to working with
any recursive data structure (see http://www.cs.chalmers.se/~patrikj/poly/).
I agree that we will have some version of unzip either way, I am just
On 8 Sep, George Russell wrote:
Don't add more functions like concatSep to the standard library or prelude.
Certainly not to the prelude, but I think there is a strong case for
evolving the standard library based on what people use. I use
((concat .) intersperse) quite a lot, and having a
Andy Gill wrote:
Simon Marlow and I are looking at including a Javadoc
like tool (Haskelldoc) as an extended example for Happy,
for release with soon to appear Happy 1.6. If only we could find
time to write it :-) A Haskelldoc program would take
a Haskell module annotated with stylized
Michael Hobbs wrote:
What's the thinking on this? As a supplement to, or instead of Literate
Haskell? Not that I've ever really used Literate Haskell, but I had
always planned on using it someday. ;-)
Literate Haskell is simply a way of including comments.
Think of it like you write a
"Michael T. Richter" wrote:
At 05:54 PM 9/8/99 , Andy Gill wrote:
I've been playing will possible formats of such documentation.
Have a look at http://www.cse.ogi.edu/~andy/gooddoc.htm
for what I'm currently thinking of.
This is what I would classify as "reasonable documentation" based
Andy's example of function documentation looks fine to me. I'd also
like to see HaskellDoc work at the module level too: define attributes
such as an author, a version, Haskell system version, export list,
imported modules, web site, repository, whatever ...
In particular, I'd really like to
I recently had occasion to write this function:
-- do a, if that fails do b, if that fails, raise b's exception
(?) :: IO a - IO a - IO a
a ? b = a `catch` \_ - b
Simple enough, but if b fails, I don't really want to raise b's
exception, I want to raise both a's exception and b's
Michael Hobbs wrote:
I think I might be able to clarify George's point with an example:
unzip. Presumably, the unzip function will stay, no matter what happens
with existential types, arrows, etc. The problem is, I don't know what
unzip *does*. (Actually, I do, but I'm taking the POV of a
Tom Pledger wrote:
Is it common OO programming practice to cast the elements of a
same-interface-different-implementation list, so as to recover the
original objects in full detail?
Hmm, that's a bit of gray area, I think. Conceptually speaking, if a
function is given a list of Shapes, it
"Erik" == Erik Meijer [EMAIL PROTECTED] writes:
The nice thing about Haskell is that the type of a polymorphic
function tells you a lot about what the function does.
So just from the type of the following polymorphic function,
what does it do?
unzap ((a,b):abs) = let bang x = x : bang x in
Are we talking about documentation for the H98 libraries?
Are these libraries relevant? Don't MPTC, Existential Types, Restricted
Type Synonyms, Arrows, and an FFI substantial change the architecture,
interface, and implementation of the libraries? As these language
features are becoming more
I think I might be able to clarify George's point with an example:
unzip. Presumably, the unzip function will stay, no matter what happens
with existential types, arrows, etc. The problem is, I don't know what
unzip *does*. (Actually, I do, but I'm taking the POV of a novice here.)
The only
[...]
unzip = foldr (\(a,b) ~(as,bs) - (a:as,b:bs)) ([],[])
Not exactly intuitive. Could be better. I'm assuming that George's point
is that this documentation leaves plenty of room for expansion.
OK, you fire up Hugs and type :t unzip and Hugs tells you that
unzip :: [(a,b)] - ([a],[b])
Hi Havoc,
Thanks for your comments about Haskell, which Manuel forward to the
Haskell list. Of the many points that you raised, one on which I
can offer some good news is the following:
| One concern that I have is the Artistic license on Hugs; this might make
| it hard to embed Hugs in other
"Michael T. Richter" wrote:
Good docs, on the other hand, are very helpful. Even if it strikes an
old-timer as redundant to explain "unzip = foldr (\(a,b) ~(as,bs) -
(a:as,b:bs)) ([],[])" as "this function takes a list of pairs and returns a
pair of lists", believe it or not this actually
At 05:54 PM 9/8/99 , Andy Gill wrote:
I've been playing will possible formats of such documentation.
Have a look at http://www.cse.ogi.edu/~andy/gooddoc.htm
for what I'm currently thinking of.
This is what I would classify as "reasonable documentation" based upon my
current level of Haskell
24 matches
Mail list logo
