Thomas Schilling wrote:

Did you try removing all .hi and .o files?

Yes. I tried it again this morning, and I've got the same error -- same unknown symbol, &c. I don't have trouble with most Haskell programs on my Mac, so I assume it's the way I'm connecting to C that is the problem. I've pasted in the relevant code below my signature -- it seems plain enough to me, but I've not done much with foreign declarations. The `Ptr Char` declarations, for example, point to things which are actually C ints -- they are all valid Unicode code points, so I figure there's no harm done. -- _jsn module Data.Char.CEDICT.Lists where import Foreign import Foreign.C import Foreign.Storable import Foreign.Marshal.Array {-# INCLUDE "c/data.h" #-} foreign import ccall unsafe "&" ts :: Ptr Char foreign import ccall unsafe "&" ts_len :: Ptr Int forTradSimp = pairUp $ readIn ts_len ts foreign import ccall unsafe "&" st :: Ptr Char foreign import ccall unsafe "&" st_len :: Ptr Int forSimpTrad = pairUp $ readIn st_len st readIn lenPtr arrPtr = unsafePerformIO $ peekArray len arrPtr where len = unsafePerformIO $ peek lenPtr pairUp [] = [] pairUp [item] = [] pairUp (a:b:rest) = (a, b):(pairUp rest) forLookup = [ ("\64013",[("huo4","to vomit")]) , ("\64012",[("wu4","duplicate of Big Five A461")]) , ("\40868",[("xie2","to harmonize / to accord with / to agree")]) , ("\40866",[("he2","harmonious")]) ]

Stefan O'Rear wrote:

The only type that you are allowed to assume corresponds to a C int is CInt, in the Foreign.C.Types module. This probably isn't the problem, but it could make problems of its own on a 64-bit or otherwise weird system.

So say I turn everything back to pointers to CInt, what is the accepted way to convert from CInt to Int and CInt to Char? Is relying on the fact that CInt always wraps a Haskell integer an okay way to go? I might was well learn these things now, before I get into bad habits. -- _jsn

On 29 Mar 2008, at 10:21 PM, Jason Dusek wrote:

Stefan O'Rear wrote:

...

The only type that you are allowed to assume corresponds to a C int is CInt, in the Foreign.C.Types module. This probably isn't the problem, but it could make problems of its own on a 64-bit or otherwise weird system.

So say I turn everything back to pointers to CInt, what is the accepted way to convert from CInt to Int

Use fromIntegral to go CInt -> Int, Int -> CInt. This only depends on CInt being an Integral type.

and CInt to Char?

Use toEnum . fromIntegral jcc

Jason Dusek wrote:

Stefan O'Rear wrote:

...

The only type that you are allowed to assume corresponds to a C int is CInt, in the Foreign.C.Types module. This probably isn't the problem, but it could make problems of its own on a 64-bit or otherwise weird system.

So say I turn everything back to pointers to CInt, what is the accepted way to convert from CInt to Int and CInt to Char?

Type class methods: -- for numbers like Int, CInt fromIntegral :: (Num b, Integral a) => a -> b -- for Char fromEnum :: (Enum a) => a -> Int toEnum :: (Enum a) => Int -> a

Is relying on the fact that CInt always wraps a Haskell integer an okay way to go?

I don't know what you mean by this.

I might was well learn these things now, before I get into bad habits.

Hope this helps, Claude -- http://claudiusmaximus.goto10.org

Bertram Felgenhauer wrote:

Jason Dusek wrote:

...

It compiles fine and loads fine -- but it doesn't run fine: unknown symbol `___stginit_cedictzm0zi1zi1_DataziCharziCEDICTziMatter_'

This is a cabal pitfall.

Thank you -- this tip saved my bacon. -- _jsn