On Friday, September 27, 2013 19:37:57 Mark wrote: > I think one can very easily expect a part called "private" to be just that > and that it should not be included. If one does do that then that person > deserves the pain when the private api changes. I don't think you should go > to private.org.kde since it breaks consistency. Or to me it looks like it > breaks consistency. org.kde.* is the consistent manner so somehow you > should figure out a way to add private included in that structure. > > Another thing, why do you even need a private import location? Can't you > simply do local privates? > > That would mean something like: > import "../private" as Private > > or something along those lines. I don't get why it has to be in a global > namespace.
How do you implement that? -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<