Heh. I was going to vote for not enough bourbons. Do note that an IV isn't always the same as an int though. An IV is always big enough to hold a pointer, and is also (therefore) big enough to hold an int. If your Inline function prototype uses an int, the value will be cast from an IV to an int for you. If you get the value yourself using SvIV() and you need it as an int, you should probably remember to cast to an int just to be safe. And maybe even check whether it's greater than MAX_INT just to be really safe.
-Ken > -----Original Message----- > From: Sisyphus [mailto:[EMAIL PROTECTED] > Sent: Sunday, September 12, 2004 2:57 AM > Cc: inline > Subject: Re: int versus SV* on Win32 > > > Sisyphus wrote: > > .... or too > > many Bourbons ? > > Yep - that was it .... I knew all along that it would be. > > Problem was simply that I have to dynamically allocate (and clean up) > the buffer in the inline C code. I was thinking that the kernel32.dll > GetTempPath function would do all that for me ... which is not very > clever thinking. > > I'll have some more bourbons anyway. > > Cheers, > Rob > >
