[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: playground/office/flake
From: Martin Ellis <m.a.ellis () ncl ! ac ! uk>
Date: 2006-05-01 18:15:40
Message-ID: 200605011915.40484.m.a.ellis () ncl ! ac ! uk
[Download RAW message or body]
On Monday 01 May 2006 18:58, Thomas Zander wrote:
> Not sure how the exporting of symbols in C++ or loadable libraries
> works, though. So I may be wrong with that.
>
> Can someone else comment on that? Is it a good idea to name
> non-exportable local classes to a name without "Ko" ?
I might be wrong, but even if it's not exported by default, I'm not
sure you can rely on everyone's build toolchain supporting
visibility.
It's only recently been introduced in g++, right?
In that case, I think the class name would be visible outside the
library, and either a prefix or a namespace would be appropriate.
Martin
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic