> > A reflective framework could be in three stages: a preprocessing stage > > (which creates the reflection data), an optional code > > generation/transformation stage, then a compilation stage. In this sense, > > it would be both a compile and run-time framework.
> Sounds like a great idea to me. A couple more questions. I'm afraid I don't have the time or expertise to create a full C++ compiler (tho it would be interesting to try using Spirit). If I were to base a reflection framework on PDT, its parser and toolset comes as binaries for the following platforms: alpha apple hp9000s700 linux rs6000 sgi32 sgin32 sgi64 solaris2 hitachi Windows t3e The actual PDT reflection library is open-source and portable. Would this be acceptable for submission to Boost? I don't know if there's a policy about library submissions depending on closed-source tools. I don't think there should be a problem (after all, most compilers Boost supports are closed-source), but it seems prudent to ask up-front. Also, it seems to me that PDT's license meets Boost's requirements. Can anyone verify this (I've appended it below)? Finally, is there anyone interested in working on a reflection framework? Does anyone have other ideas on approaching this problem? Any comments at all? I'll consolidate the information and put them up on the Wiki board. Were talking exclusively about reflection now... I don't want this muddled with the serialization discussion. They are separate topics. :-) TIA, --craig ********************************************************************************* ** Program Database Toolkit ** ** http://www.acl.lanl.gov/pdtoolkit ** ********************************************************************************* ** Copyright 1998-2002 ** ** Department of Computer and Information Science, University of Oregon ** ** Research Center Juelich, ZAM, Germany ** ** Advanced Computing Laboratory, Los Alamos National Laboratory ** ********************************************************************************* ** ** ** Permission to use, copy, modify, and distribute this software and its ** ** documentation for any purpose and without fee is hereby granted, ** ** provided that the above copyright notice appears in all copies and that ** ** both that copyright notice and this permission notice appear in ** ** supporting documentation, and that the name of University of Oregon (UO), ** ** Research Center Juelich (ZAM), and Los Alamos National Laboratory (LANL) ** ** not be used in advertising or publicity pertaining to distribution of ** ** the software without specific, written prior permission. The ** ** University of Oregon, ZAM, and LANL make no representations about the ** ** suitability of this software for any purpose. It is provided "as is" ** ** without express or implied warranty. ** ** ** ** UO, ZAM, AND LANL DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE. ** ** IN NO EVENT SHALL THE UNIVERSITY OF OREGON, ZAM, OR LANL BE LIABLE FOR ** ** ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER ** ** RESULTING FROM LOSS OF USE, DATA, OR PROFITS, WHETHER IN AN ACTION OF ** ** CONTRACT, NEGLIGENCE, OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN ** ** CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. ** ** ** ********************************************************************************* _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
