[c2hs] #37: Export C2HS.hs module from library part of the c2hs package

[GHC]

#37: Export C2HS.hs module from library part of the c2hs package
--------------------+-------------------------------------------------------
 Reporter:  guest   |        Type:  enhancement
   Status:  new     |    Priority:  normal    
Milestone:          |   Component:  general    
  Version:  0.16.0  |    Keywords:            
--------------------+-------------------------------------------------------
 I see some packages (portaudio, alsa) at Hackage, that contain a plain
 copy of the C2HS module. Wouldn't it be better to add a library part to
 the c2hs package and export the C2HS module?

--
Ticket URL: <http://hackage.haskell.org/trac/c2hs/ticket/37>
c2hs <http://www.cse.unsw.edu.au/~chak/haskell/c2hs/>
C->Haskell, An Interface Generator for Haskell

_______________________________________________
C2hs mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/c2hs

[GHC]

#37: Export C2HS.hs module from library part of the c2hs package
--------------------+-------------------------------------------------------
 Reporter:  guest   |         Type:  enhancement
   Status:  closed  |     Priority:  normal    
Milestone:          |    Component:  general    
  Version:  0.16.0  |   Resolution:  wontfix    
 Keywords:          |  
--------------------+-------------------------------------------------------
Changes (by duncan):

  * status:  new => closed
  * resolution:  => wontfix


Comment:

 No, this is deliberate. We do not want to force a runtime dependency on
 c2hs. The longer term plan is to eliminate the need for the C2HS module
 completely, it's just a bunch of simple marshalling utilities.

--
Ticket URL: <http://hackage.haskell.org/trac/c2hs/ticket/37#comment:1>
c2hs <http://www.cse.unsw.edu.au/~chak/haskell/c2hs/>
C->Haskell, An Interface Generator for Haskell

_______________________________________________
C2hs mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/c2hs