If it is really needed this argues more for introducing inheritance as an interim and then remove it eg generate a warning saying obsolete or something.Though I have seen C++ code converted to C using structs and some indirection to mimic inheritance so the same is also possible.
Ben From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan S. Shapiro Sent: Monday, April 04, 2011 2:57 PM To: Discussions about the BitC language Subject: Re: [bitc-dev] Inheritance and Existentialism On Sat, Apr 2, 2011 at 7:01 AM, Sandro Magi <[email protected]> wrote: Do you have some argument or examples that contradict this conclusion? What sort of scenarios push you toward a traditional OO structure? Yes. And it's depressingly practical. I have this large-ish body of C++ code. At last measurement it was about 45,000 lines. I'ld like to convert this application to BitC. Over time, I'm willing to do idiom conversion, but the engineering reality is that I need to do that in a phased way. So I need a way to convert the code in such a way that it remains comprehensible to the developers who are familiar with the current code. [ Note: the conversion is likely to be done by hand, which is a very strong reason to deal with one problem at a time. ] The code base? Well, some dickhead went and built a BitC compiler in C++... Moral: we need something that is "textually similar" to inheritance for transitional purposes.
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
