Sounds pretty cool, David.
A plodder like me is probably just going to stick with Inline, but it would be
great to see C::Blocks takes off. And it has the attractiveness to do so.
(I like the way you can so easily just plonk the C code right in there amongst
the perl code makes Inline look
From: Bill Moseley
Sent: Tuesday, September 30, 2014 10:39 PM
Is there potential for symbols to clash in this situation?
No.
It should not be possible for the set up you described to result in a
clash of XS symbols, no matter how hard you try. The XS symbols are
private to both modules -
From: Bill Moseley
Sent: Wednesday, October 01, 2014 1:12 AM
To: perl-xs@perl.org
Subject: Re: Two XS modules linked to one .a library.
Just to clarify I was meaning the symbols in the shared third-party .a
library. Where two separate Perl (XS) modules link to the same static .a
library and
From: Bill Moseley
Sent: Wednesday, October 01, 2014 1:12 AM
To: perl-xs@perl.org
Subject: Re: Two XS modules linked to one .a library.
Just to clarify I was meaning the symbols in the shared third-party .a
library.
Afterthought:
The 3rd party .a library is not really shared.
When you build
From: David Mertens
Sent: Monday, April 25, 2016 7:16 AM
To: perl-xs@perl.org
Subject: Help setting up appveyor for Windows continuous integration testing
Hello everyone,
The specific tcc error (given at
https://ci.appveyor.com/project/run4flat/c-blocks/build/1.0.17#L47) is:
-Original Message-
From: Erland Sommarskog
Sent: Thursday, July 14, 2016 2:18 AM
To: perl-xs@perl.org
Subject: loadable library and perl binaries are mismatched
I have an XS module to permit Perl scripts access SQL Server through OLE
DB.
Besides a source-code only distribution, I also
