Re: [dylan] The Future of Dylan: What do we use it for?
Bruce Hoult <[email protected]> Tue, 9 Sep 2014 17:10:44 +1200
| Newsgroups | gmane.comp.lang.dylan.gwydion.devel |
|---|---|
| Message-ID | <CAMU+EkyPe8BD7ERfSLKDVz6KcvVVxp8v+8py_r7aisApYEppJQ@mail.gmail.com> |
--===============0097477087== Content-Type: multipart/alternative; boundary=001a1134cc6827e33605029af5c2 --001a1134cc6827e33605029af5c2 Content-Type: text/plain; charset=UTF-8 You would think that these days it would be pretty easy to get clang (or gcc) to output pure C header files containing struct, function and (maybe) macro definitions corresponding to C++ headers. The main requirement would be, I think, standardising and documenting the mangling algorithm that makes it all work with C-era linkers anyway. On Tue, Sep 9, 2014 at 5:04 PM, Scott McKay <[email protected]> wrote: > FWIW, even inside of Google, C++ is not directly wrapped. You write C > wrappers first, then export those wrappers for FFI use by, eg, Lisp or > Python. "Nobody" supports FFI over C++. > > > --Scott > > > On Sep 9, 2014, at 3:12 AM, Bruce Mitchener <[email protected]> > wrote: > > > > C++ would be pretty difficult / a lot of work. The process of wrapping C > APIs could be better though. As you say, we could use libclang to implement > parts of melange. That's a decent amount of work, but doable. > _______________________________________________ > hackers mailing list > [email protected] > https://lists.opendylan.org/mailman/listinfo/hackers > --001a1134cc6827e33605029af5c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">You would think that these days it would be pretty easy to= get clang (or gcc) to output pure C header files containing struct, functi= on and (maybe) macro definitions corresponding to C++ headers.<div><br></di= v><div>The main requirement would be, I think, standardising and documentin= g the mangling algorithm that makes it all work with C-era linkers anyway.<= /div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On= Tue, Sep 9, 2014 at 5:04 PM, Scott McKay <span dir=3D"ltr"><<a href=3D"= mailto:[email protected]" target=3D"_blank">[email protected]</a>></span= > wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo= rder-left:1px #ccc solid;padding-left:1ex">FWIW, even inside of Google, C++= is not directly wrapped. You write C wrappers first, then export those wra= ppers for FFI use by, eg, Lisp or Python. "Nobody" supports FFI o= ver C++.<br> <span class=3D"HOEnZb"><font color=3D"#888888"><br> <br> --Scott<br> </font></span><span class=3D"im HOEnZb"><br> > On Sep 9, 2014, at 3:12 AM, Bruce Mitchener <<a href=3D"mailto:bruc= [email protected]">[email protected]</a>> wrote:<br> ><br> > C++ would be pretty difficult / a lot of work. The process of wrapping= C APIs could be better though. As you say, we could use libclang to implem= ent parts of melange. That's a decent amount of work, but doable.<br> </span><div class=3D"HOEnZb"><div class=3D"h5">____________________________= ___________________<br> hackers mailing list<br> <a href=3D"mailto:[email protected]">[email protected]<= /a><br> <a href=3D"https://lists.opendylan.org/mailman/listinfo/hackers" target=3D"= _blank">https://lists.opendylan.org/mailman/listinfo/hackers</a><br> </div></div></blockquote></div><br></div> --001a1134cc6827e33605029af5c2-- --===============0097477087== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ hackers mailing list [email protected] https://lists.opendylan.org/mailman/listinfo/hackers --===============0097477087==--