Rene Rivera <[EMAIL PROTECTED]> writes: > David Abrahams wrote: >> Rene Rivera <[EMAIL PROTECTED]> writes: >> >> I don't know what that diagram is supposed to illustrate. >> >>> It could just as easily be: in-memory -> PHP/Python/Perl. >> >> Not just as easily, because then you have to write bindings for each >> backend language. > > I was trying to show that doing binding translations for in-memory > structures is at worse as hard as the translations for dealing with an > XML on-disk representation.
I know that's what you're claiming, but I don't think you did anything to "show" it. I understand the claim, but I don't believe it, sorry. > And that since most languages already deal with ABI issues they > already do most of the in-memory data translation for you. I guess I don't know what that means. -- Dave Abrahams Boost Consulting www.boost-consulting.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
