Re: ffi library port to Windows

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1661827358==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig176F59F51E78E39297694328"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig176F59F51E78E39297694328
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Enrico,

Enrico Migliore wrote:
> 1. directory tree
> ----------------
> 
> The ctypes guys, instead of adding #ifdef's to the original source files
> of ffi, decided to make a copy of the following files:
> ...
> That means that GCC and MSVC work on different source files. A while
> ago, we agreed on adding #ifdef wherever possible, in order to have just
> one source tree. What are we supposed to do?

I would say:  we should do as is done elsewhere in libffi.  I think that
for assembly language files, libffi puts the code in separate files, but
for most other things uses the same source files.  Yet, maybe this is
not practical.  I would leave it to your good judgment to make the call...

> 2. license issue
> ---------------
> Am I supposed to ask for permission to the Ctpye guys, before re-working
> and submitting the source files to the SableVM project?

Are you dropping all the work you had already done?  I was pointing this
work as I discovered it by accident, more or less, to help you if
validate your work, not necessarily to use it.

Yet, CType's license seems OK.  But, It would be unclean for you to mix
and merge sablevm's libffi and CType's libffi in your working copy; we
would lose clear copyright trail. :-(

So, could you tell me more about the status of your previous work,
first, before we decide to merge CType's code?


-- 
Etienne M. Gagnon, Ph.D.            http://www.info2.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/

--------------enig176F59F51E78E39297694328
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEcgUEjyrJi4rH84gRAvkWAJwLbA6cBFTBWepQqiStuQazZwxIgwCeK8lw
3gRsAybv2lNn5vg+kWbbFlQ=
=rlng
-----END PGP SIGNATURE-----

--------------enig176F59F51E78E39297694328--


--===============1661827358==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SableVM-user mailing list
[email protected]
http://sablevm.org/lists/control/listinfo/sablevm-user

--===============1661827358==--