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. And that since most languages already deal with ABI issues they already do most of the in-memory data translation for you. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo ------------------------------------------------------------------------- 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
