Ok, I think I undersatnd now, you want the objective C implementation
(SalFrameWindow and SalFrameView) in a separate .mm file with an own header.
No problem, it probably is cleaner that way with the additional
advantage that we won't lose the history on e.g. salframe.cxx.
I'll do it that way then.
Kind regards, pl
Michael Sicotte wrote:
On Oct 9, 2007, at 10:21 AM, Philipp Lohmann wrote:
Sorry, I'm not quite sure what the structure you mentioned would look
like. Taking AquaSalFrame as an example (which is currently in
vcl/aqua/inc/salframe.h and vcl/aqua/source/window/salframe.cxx) what
would you put where ? What I would have done would be simply to rename
what is .cxx now to .mm afterwards.
Dear Philipp,
Taking salframe.cxx as an example, the class AquaSalFrame (the main
class in the file) is implemented in C++. I would expect the the main
class in the file should be implemented in Objective-C++ in a file with
the .mm extension.
I wrote a blog post here with a longer answer.
In the end, its ok with me if the consensus is for renaming the files.
As EricB told me, OpenOffice.org is oceans of code. I think that there
is room for a lot of diversity in the ocean.
Regards,
Mike
--
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them for a lifetime.
-- Author unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
