On Thu, Oct 06, 2005 at 09:24:19PM -0400, Nathanael Nerode wrote:
Brian Carlson wrote:
You must not pass by reference with an extern C declaration, because C
doesn't support that.
Dan Jacobowitz wrote:
Why not? An extern C definition doesn't mean that it needs to be
usable from C. It
Scripsit Brian M. Carlson [EMAIL PROTECTED]
On Thursday 06 October 2005 12:45, Henning Makholm wrote:
I notice that the newest upload of pstoedit has reverted the C++
transition name change; instead of libpstoedit0c2 sid now contains
libpstoedit0, as in sarge.
Does this not need
Scripsit Brian M. Carlson [EMAIL PROTECTED]
On Thursday 06 October 2005 12:45, Henning Makholm wrote:
I notice that the newest upload of pstoedit has reverted the C++
transition name change; instead of libpstoedit0c2 sid now contains
libpstoedit0, as in sarge.
This is, IMHO, incorrect.
It
I notice that the newest upload of pstoedit has reverted the C++
transition name change; instead of libpstoedit0c2 sid now contains
libpstoedit0, as in sarge.
However, the library exports things with interfaces such as
#ifdef __cplusplus
extern C DLLEXPORT
int pstoeditwithghostscript(int argc,
On Thursday 06 October 2005 12:45, Henning Makholm wrote:
I notice that the newest upload of pstoedit has reverted the C++
transition name change; instead of libpstoedit0c2 sid now contains
libpstoedit0, as in sarge.
This is, IMHO, incorrect.
However, the library exports things with
On 10/6/05, Brian M. Carlson [EMAIL PROTECTED] wrote:
On Thursday 06 October 2005 12:45, Henning Makholm wrote:
I notice that the newest upload of pstoedit has reverted the C++
transition name change; instead of libpstoedit0c2 sid now contains
libpstoedit0, as in sarge.
This is, IMHO,
On Thu, Oct 06, 2005 at 05:35:34PM +, Brian M. Carlson wrote:
On Thursday 06 October 2005 12:45, Henning Makholm wrote:
I notice that the newest upload of pstoedit has reverted the C++
transition name change; instead of libpstoedit0c2 sid now contains
libpstoedit0, as in sarge.
This
Brian Carlson wrote:
You must not pass by reference with an extern C declaration, because C
doesn't support that.
Dan Jacobowitz wrote:
Why not? An extern C definition doesn't mean that it needs to be
usable from C. It just means to use the C calling convention.
Perhaps because there is no C
8 matches
Mail list logo