"Jason Dagit" <[EMAIL PROTECTED]> writes:
>> 2) Compile GHC yourself.
> I find with Debian this is the way to go.
Ouch. Okay, I've compiled GHC once. But I would like end-users to be
able to use my software, and I simply cannot require them to go
through this.
> Install your system and use D
"Jeremy Shaw" <[EMAIL PROTECTED]> writes:
I probably shouldn't post when I don't quite understand the question,
and I'm unsure whether this is about timeouts, lazy parsing of
responses, or line endings? These seem like independent issues to
me. Anyway:
> Polyparse has some lazy parsers:
but To
On Mon, Aug 25, 2008 at 9:10 AM, Mads Lindstrøm
<[EMAIL PROTECTED]> wrote:
> Hi
>
> Ketil Malde wrote:
>> I've had an interested user, who tried to get one of my programs to
>> run on a Debian machine - running Debian Etch, released a couple of
>> months ago. Here are some of the hurdles stumbled
Hello,
I'm trying to build the latest SDL-image package (0.5.2) from Hackage on
Windows and encountering problems. These are the steps I've taken so far:
1. Downloaded SDL 1.2.13 developmental library for Mingw32 to
E:\SDL-1.2.13, and SDL_image 1.2.6 developmental library for VC8 to
E:\SDL_imag
David Roundy wrote:
> Which illustrates the point that it's not type safety
> that protects us from segfaults, so much as bounds checking,
> and that's got a non-trivial runtime cost. At least, most
> segfaults that *I've* caused (in C or C++) have been from
> overwriting the bounds of arrays,
Lennart Augustsson wrote:
The values Z, S Z, and S (S Z) all have the same runtime
representation and there is no linear increase in size when you add a
extra S.
BUT, if you make something overloaded and there is a dictionary
associated with the type (Z, S Z, or S (S Z)) then the dictionary
take
On Wed, 2008-08-27 at 01:48 +0200, Wolfgang Jeltsch wrote:
> Hello,
>
> Haskell is non-strict but not necessarily lazy. So it’s possible that an
> expression is reduced to WHNF although it is not used yet. Could this “early
> reduction” also happen to outputs of unsafeInterleaveIO actions (whi
Lennart Augustsson wrote:
No hardware drivers use global variables.
No problem, write your hardware drivers in a different monad. Thus IO is
the type for code that can use global variables, and H (or whatever) is
the type for code that must not.
--
Ashley Yakeley
___
BTW, I'm not contradicting that the use of global variables can be
necessary when interfacing with legacy code, I just don't think it's
the right design when doing something new.
-- Lennart
On Tue, Aug 26, 2008 at 9:47 PM, Adrian Hey <[EMAIL PROTECTED]> wrote:
> Lennart Augustsson wrote:
>>
>>
I told you where to look at code. It's C code, mind you, but written
in a decent way.
No well written device driver ever accesses memory or IO ports
directly, doing so would seriously hamper portability.
Instead you use an abstraction layer to access to hardware, and the
driver gets passed a "bus"
Wolfgang,
> Haskell is non-strict but not necessarily lazy. So it's possible
> that an expression is reduced to WHNF although it is not used yet.
> Could this early reduction also happen to outputs of
> unsafeInterleaveIO actions (which might trigger the action too early)?
> While I'd expect thos
John Meacham <[EMAIL PROTECTED]> wrote:
> Your company does whatever the buzzword that the venture
> capitalist you are currently talking to is enthralled with. :)
Then we'll need some green, renewable monads!
--
_jsn
___
Haskell-Cafe mailing list
Has
On Wed, Aug 20, 2008 at 03:17:14PM -0700, Jason Dusek wrote:
> What is your company going to do?
What sort of dot-com attitude is that? Your company does whatever the
buzzword that the venture capitalist you are currently talking to is
enthralled with. :)
'monadic B2B ultra-wideband catamorphic
On Tue, Aug 26, 2008 at 08:07:24AM +0100, Adrian Hey wrote:
> But from a top level aThing <- someACIO point of view, if we're going to
> say that it doesn't matter if someACIO is executed before main is
> entered (possibly even at compile time) or on demand, then we clearly
> don't want to observe
On Tue, Aug 26, 2008 at 01:14:34AM -0700, Judah Jacobson wrote:
> On Tue, Aug 26, 2008 at 12:07 AM, Adrian Hey <[EMAIL PROTECTED]> wrote:
> >
> >
> > But from a top level aThing <- someACIO point of view, if we're going to
> > say that it doesn't matter if someACIO is executed before main is
> > en
Hello,
Haskell is non-strict but not necessarily lazy. So it’s possible that an
expression is reduced to WHNF although it is not used yet. Could this “early
reduction” also happen to outputs of unsafeInterleaveIO actions (which might
trigger the action too early)? While I’d expect those outp
On Tue, 2008-08-26 at 15:31 -0700, Bryan O'Sullivan wrote:
> On Tue, Aug 26, 2008 at 3:04 PM, Don Stewart <[EMAIL PROTECTED]> wrote:
>
> > No, since I can get whnf with `seq`. However, that does sound like a
> > good idea (a patch to the parallel library? )
>
> I suspect that patching parallel do
On Mon, 2008-08-25 at 23:22 -0700, John MacFarlane wrote:
> I've written a library, zip-archive, for dealing with zip archives.
Great. I saw your query about this from a month ago.
> Haddock documentation (with links to source code):
> http://johnmacfarlane.net/zip-archive/
>
> Darcs repository
On Tue, 2008-08-26 at 15:53 +0100, Claus Reinke wrote:
> > GHC knows what the problem is but it's just following orders. Cabal gave
> > the orders but doesn't know there is a problem.
>
> Since you said "don't hold your breath for Cabal's dependencies":
> Cabal doesn't have to pass on ghc's messa
On Tue, Aug 26, 2008 at 3:43 PM, John Van Enk <[EMAIL PROTECTED]> wrote:
> Perhaps you'll want to continue with the hGetLine setup in one thread
> (assuming the NNTP data is line delimited), then in another, parse the data,
> then in a third, respond.
Sorry if my writing was unclear. I think hGetL
On Tue, Aug 26, 2008 at 3:04 PM, Don Stewart <[EMAIL PROTECTED]> wrote:
> No, since I can get whnf with `seq`. However, that does sound like a
> good idea (a patch to the parallel library? )
I suspect that patching parallel doesn't scale. It doesn't have a
maintainer, so it will be slow, and the
On Tue, 26 Aug 2008, John Van Enk wrote:
I think the problem I'll run into is the 128 channel case. I'm hoping for a
general solution... I'm almost positive this will require runtime checks.
Your solution is what I was thinking for functions requiring exactly N
channels (I'm not sure if there a
On Tue, Aug 26, 2008 at 2:49 PM, Tim Newsham <[EMAIL PROTECTED]> wrote:
> Like everyone else who has used Haskell for a while, I'm accumulating
> functions which I feel should have already been in the standard
> libraries. What's the normal path to contributing functions for
> consideration in fut
Judah Jacobson wrote:
> I think you're saying that you want to write "w <- newIOWitness" at
> the top level, so that w can then be referenced in a pure function.
> Fair enough. But newIOWitness's implementation requires writeIORef
> (or an equivalent), which is not ACIO, right?
newIOWitness is ve
bos:
> On Mon, Aug 25, 2008 at 2:28 PM, Don Stewart <[EMAIL PROTECTED]> wrote:
>
> > I've pushed a decodeFile that does a whnf on the tail after decoding.
>
> Does this mean that there are now NFData instances for bytestrings?
> That would be handy.
No, since I can get whnf with `seq`. However,
functions which I feel should have already been in the standard
libraries.
have you tried searching with "hoogle" for the types of your functions.
signature.asc
Description: OpenPGP digital signature
___
Haskell-Cafe mailing list
Haskell-Cafe@h
On Mon, Aug 25, 2008 at 2:28 PM, Don Stewart <[EMAIL PROTECTED]> wrote:
> I've pushed a decodeFile that does a whnf on the tail after decoding.
Does this mean that there are now NFData instances for bytestrings?
That would be handy.
___
Haskell-Cafe mai
On 2008 Aug 26, at 17:49, Tim Newsham wrote:
Like everyone else who has used Haskell for a while, I'm accumulating
functions which I feel should have already been in the standard
libraries. What's the normal path to contributing functions for
consideration in future standard libraries? Is there
Like everyone else who has used Haskell for a while, I'm accumulating
functions which I feel should have already been in the standard
libraries. What's the normal path to contributing functions for
consideration in future standard libraries? Is there some
experimental standard lib that we can co
Hello,
Polyparse has some lazy parsers:
http://www.cs.york.ac.uk/fp/polyparse/
Perhaps that would do the trick?
j.
At Tue, 26 Aug 2008 15:35:28 -0500,
brian wrote:
>
> Hi, I've been struggling with this problem for days and I'm dying. Please
> help.
>
> I want to use Parsec to parse NNTP da
Lennart Augustsson wrote:
Making a network stack from peek and poke is easy in a well structured OS.
The boot loader (or whatever) hands you the capability (call it
something else if you want) to do raw hardware access, and you build
from there. If you look at well structured OSs like NetBSD, th
Perhaps you'll want to continue with the hGetLine setup in one thread
(assuming the NNTP data is line delimited), then in another, parse the data,
then in a third, respond.
Lookup how to use MVar's. Allowing the threads to block on reads/writes is a
lot easier (logically) than figuring out the mes
On Tue, Aug 26, 2008 at 3:38 PM, John Van Enk <[EMAIL PROTECTED]> wrote:
> Are you doing this all in a single thread?
Yes.
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
Are you doing this all in a single thread?
On Tue, Aug 26, 2008 at 4:35 PM, brian <[EMAIL PROTECTED]> wrote:
> Hi, I've been struggling with this problem for days and I'm dying. Please
> help.
>
> I want to use Parsec to parse NNTP data coming to me from a handle I
> get from connectTo.
>
> One u
Hi, I've been struggling with this problem for days and I'm dying. Please help.
I want to use Parsec to parse NNTP data coming to me from a handle I
get from connectTo.
One unworkable approach I tried is to get a lazy String from the
handle with hGetContents. The problem: suppose the first messag
On Tue, Aug 26, 2008 at 3:15 AM, Ashley Yakeley <[EMAIL PROTECTED]> wrote:
> Judah Jacobson wrote:
>>
>> I've been wondering: is there any benefit to having top-level ACIO'd
>> <- instead of just using runOnce (or perhaps "oneshot") as the
>> primitive for everything?
>
> I don't think oneshots are
I think the problem I'll run into is the 128 channel case. I'm hoping for a
general solution... I'm almost positive this will require runtime checks.
Your solution is what I was thinking for functions requiring exactly N
channels (I'm not sure if there are many functions like that).
On Tue, Aug
The values Z, S Z, and S (S Z) all have the same runtime
representation and there is no linear increase in size when you add a
extra S.
BUT, if you make something overloaded and there is a dictionary
associated with the type (Z, S Z, or S (S Z)) then the dictionary
takes up space, and that space is
On Mon, 25 Aug 2008, John Van Enk wrote:
How well would the storablevector package (Data.StorableVector) work for
storing audio data? One of the major issues I'm still working over is that I
want to maintain something similar to a [[a]] format (since the underlying
PortAudio library and hardwar
On Tue, 2008-08-26 at 18:34 +0100, Adrian Hey wrote:
> I have a feeling this is going to be a very long thread so I'm trying
> to go to Haskell cafe again (without mucking it up again).
>
> Derek Elkins wrote:
> > Haskell should be moving -toward- a capability-like model, not away from
> > it.
>
igouy2:
>
> --- Don Stewart <[EMAIL PROTECTED]> wrote:
>
> -snip-
>
> > So still consolidating the system.
>
> Pretty much.
>
>
> > Do I understand though, that if we submit, say, a quad-core version
> > of
> > binary-trees, for example, using `par` and -N4, it'll go live on the
> > benchma
--- Don Stewart <[EMAIL PROTECTED]> wrote:
-snip-
> So still consolidating the system.
Pretty much.
> Do I understand though, that if we submit, say, a quad-core version
> of
> binary-trees, for example, using `par` and -N4, it'll go live on the
> benchmark page?
That's an open question -
Making a network stack from peek and poke is easy in a well structured OS.
The boot loader (or whatever) hands you the capability (call it
something else if you want) to do raw hardware access, and you build
from there. If you look at well structured OSs like NetBSD, this is
pretty much how they w
igouy2:
> > dons:
>
> > (Where I note GHC is currently in second place, though we've not
> > submitted any parallel programs yet).
>
> We might call that the thread-ring effect :-)
>
>
> > Also CC'd Isaac, Mr. Shootout. Isaac, is the quad core shootout
> > open for business? Should we rally the
Ryan Ingram wrote:
> wren ng thornton wrote:
>> It should also be noted that the overhead for newtypes is not *always*
>> removed. In particular, if we have the following definitions:
>>
>>dataZ = Z
>>newtype S a = S a
>>
>> We must keep the tags (i.e. boxes) for S around because (S Z
> dons:
> (Where I note GHC is currently in second place, though we've not
> submitted any parallel programs yet).
We might call that the thread-ring effect :-)
> Also CC'd Isaac, Mr. Shootout. Isaac, is the quad core shootout
> open for business? Should we rally the troops?
iirc there was som
I have a feeling this is going to be a very long thread so I'm trying
to go to Haskell cafe again (without mucking it up again).
Derek Elkins wrote:
Haskell should be moving -toward- a capability-like model, not away from
it.
Could you show how to implement Data.Random or Data.Unique using suc
dmehrtash:
>Bjorn,
>I am initializing a list from a file. I am reading the lines from the
>file, splitting them into bytestring and then converting them to float.
>Should I be using String -> Float or ByteString -> Float?
I'd try reading the file entirely as a bytestring,
then s
Bjorn,
I am initializing a list from a file. I am reading the lines from the file,
splitting them into bytestring and then converting them to float. Should I
be using String -> Float or ByteString -> Float?
thanks
Daryoush
On Tue, Aug 26, 2008 at 6:01 AM, Bjorn Bringert <[EMAIL PROTECTED]> wro
On Tue, Aug 26, 2008 at 1:19 AM, wren ng thornton <[EMAIL PROTECTED]> wrote:
> It should also be noted that the overhead for newtypes is not *always*
> removed. In particular, if we have the following definitions:
>
>dataZ = Z
>newtype S a = S a
>
> We must keep the tags (i.e. boxes)
On Tue, 2008-08-26 at 20:18 +0400, Bulat Ziganshin wrote:
> Hello Derek,
>
> Tuesday, August 26, 2008, 8:14:21 PM, you wrote:
>
> >> but from my POV it's important to push this feature into haskell
> >> standard
>
> > Haskell should be moving -toward- a capability-like model, not away from
> > i
Hello Derek,
Tuesday, August 26, 2008, 8:14:21 PM, you wrote:
>> but from my POV it's important to push this feature into haskell
>> standard
> Haskell should be moving -toward- a capability-like model, not away from
> it.
what you mean by "capability-like model"?
--
Best regards,
Bulat
First thanks you two for the reply.
Now for the solution, I'm a bit ashamed of myself, because I simply forgot
to put a
clientState VertexArray $= Enabled
The rest of the code is valid beside this 'little' miss
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la pa
thank you very much for the explanation!
i take that in this case, the error is in the cabal, which does not list
the required package.
andrew
On Tue, 2008-08-26 at 15:09 +0100, Duncan Coutts wrote:
> On Tue, 2008-08-26 at 14:30 +0100, Dougal Stanton wrote:
> > On Tue, Aug 26, 2008 at 2:22 PM, Du
[snip]
>
> Most probably you are confusing type and data constructor. This is a common
> error and a hurdle I remember falling over more than once. It is due to the
> fact that in Haskell both are in completely separate name spaces,
> nevertheless both use capitalized names. Thus people often use
> So when ghc finds that one of your modules needs to import something
> that is not in one of the given packages it says that it's in another
> package that is 'hidden'. Of course it's only hidden because Cabal told
> ghc to hide them.
Yes, it is one of those unfortunate error messages that says
On Tue, 2008-08-26 at 14:30 +0100, Dougal Stanton wrote:
> On Tue, Aug 26, 2008 at 2:22 PM, Duncan Coutts
> <[EMAIL PROTECTED]> wrote:
>
> > So when ghc finds that one of your modules needs to import something
> > that is not in one of the given packages it says that it's in another
> > package th
On Sat, Aug 23, 2008 at 6:15 PM, Daniel Fischer
<[EMAIL PROTECTED]> wrote:
> Am Samstag, 23. August 2008 23:17 schrieb Thomas Davie:
>>
>> I'd be interested to see your other examples -- because that error is
>> not happening in Haskell! You can't argue that Haskell doesn't give
>> you no segfault
On Tue, Aug 26, 2008 at 2:22 PM, Duncan Coutts
<[EMAIL PROTECTED]> wrote:
> So when ghc finds that one of your modules needs to import something
> that is not in one of the given packages it says that it's in another
> package that is 'hidden'. Of course it's only hidden because Cabal told
> ghc t
On Tue, 2008-08-26 at 12:06 +0200, Andrew U. Frank wrote:
> in fairness, i have to add that i did inadvertetly install version 0.3.
> of syb-with-class and got the error i still cannot understand.
>
> installing version 0.4 did work flawlessly!
>
> nevertheless, i would be interested to understan
2008/8/24 Daryoush Mehrtash <[EMAIL PROTECTED]>:
> I am trying to convert a string to a float. It seems that Data.ByteString
> library only supports readInt.After some googling I came accross a
> possibloe implementation: http://sequence.svcs.cs.pdx.edu/node/373
>
> My questions are:
>
> a) is
> > Wow! 3x the performance for a simple change. Frustrating that there
> > isn't a protable/standard way to express this. Also frustrating that
> > the threaded version doesn't improve on the situation (utilization is
> > back at 50%).
GR, retraction, retraction!
I was obviously too tired
> Is it allowed to write two
> different modules in a single
> file? Something like:
>
> module Mod1 (...) where {
> ...
> }
>
> module Mod2 (...) where {
> import Mod1;
> ...
> }
>
> I tried, and got an error,
> but would like to confirm
> that there's no way to do
> that.
No, th
Judah Jacobson wrote:
I've been wondering: is there any benefit to having top-level ACIO'd
<- instead of just using runOnce (or perhaps "oneshot") as the
primitive for everything?
I don't think oneshots are very good for open witness declarations (such
as the open exceptions I mentioned origin
in fairness, i have to add that i did inadvertetly install version 0.3.
of syb-with-class and got the error i still cannot understand.
installing version 0.4 did work flawlessly!
nevertheless, i would be interested to understand the problem i
encountered.
andrew
On Mon, 2008-08-25 at 18:08 +020
Adrian Hey wrote:
Maybe it would be safest to just say anything with a finaliser can't be
created at the top level.
Do you have an example of something that is correctly ACIO to create,
but has a problematic finaliser?
--
Ashley Yakeley
___
Haskell
Hans van Thiel wrote:
As a general comment on the teaching of Haskell, all books and
tutorials, which I've seen, appear to treat this aspect of Haskell as if
it were self explanatory. This while the better known imperative
languages don't have anything like it. Only Real World Haskell explains
al
On Tue, Aug 26, 2008 at 12:07 AM, Adrian Hey <[EMAIL PROTECTED]> wrote:
>
>
> But from a top level aThing <- someACIO point of view, if we're going to
> say that it doesn't matter if someACIO is executed before main is
> entered (possibly even at compile time) or on demand, then we clearly
> don't
John Meacham wrote:
I forgot who came up with the original ACIO idea, but I'd give them
props in the manual if they wish.
I think this is based on Ian Starks message..
http://www.haskell.org/pipermail/haskell-cafe/2004-November/007664.html
Yeah, this sounds like a great idea. there were a wh
69 matches
Mail list logo
