Inline. On Mon, 2002-11-11 at 16:40, Zaphod wrote: > On Mon, Nov 11, 2002 at 11:04:09AM -0500, Jonathan Pryor wrote: > > Well, I haven't used the new compiler, I've just read the presentation > > slides. I would imagine that it would generate the same IL. > > So this is a rebirth of the C++ void foo::bar() declaration model > Right ?.. (old wine, new package). But well there's hype for you :-) > "New Feature" ... partial types ...
Sort of, yes. It looks to be the C++ `void foo::bar()' implementation model, except you don't need the header file/class declaration. Meaning that you don't need to keep the member function declaration and member function definition in sync with each other. Instead of naming the member function in two places (declaration and definition), there's only one. This should ease maintenance. So it's more of a "old wine, added ingredients" package... What they don't specify is how base classes and attributes are handled. Must the same bases and attributes be specified on all the partial classes, or does the resulting class have the union of all attributes and base classes used in the partial class definitions? This could be confusing to maintenance programmers. <snip/> - Jon _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
