On Wednesday 07 November 2012 17:41:15 Kevin Ottens wrote:
> On Wednesday 07 November 2012 16:50:39 David Faure wrote:
> > On Monday 29 October 2012 07:40:29 Kevin Ottens wrote:
> > > Generated forward headers definitely have my preference as they indeed
> > > separate the include organization from
On Wednesday 07 November 2012 16:50:39 David Faure wrote:
> On Monday 29 October 2012 07:40:29 Kevin Ottens wrote:
> > Generated forward headers definitely have my preference as they indeed
> > separate the include organization from the "implementation detail" of how
> > the sources are organized.
On Monday 29 October 2012 07:40:29 Kevin Ottens wrote:
> On Thursday 25 October 2012 00:13:23 David Faure wrote:
> > Our standard directory structure for frameworks is like
> > staging/kwidgets/src/dialogs/kdialog.h
> > where "dialogs" is an arbitrary subdir name,
> > which works fine for such easy
On Thursday 25 October 2012 00:13:23 David Faure wrote:
> Our standard directory structure for frameworks is like
> staging/kwidgets/src/dialogs/kdialog.h
> where "dialogs" is an arbitrary subdir name,
> which works fine for such easy cases (#include )
>
> But what about frameworks which want to us
On Thursday 25 October 2012, David Faure wrote:
> Our standard directory structure for frameworks is like
> staging/kwidgets/src/dialogs/kdialog.h
> where "dialogs" is an arbitrary subdir name,
> which works fine for such easy cases (#include )
>
> But what about frameworks which want to use a nam
Our standard directory structure for frameworks is like
staging/kwidgets/src/dialogs/kdialog.h
where "dialogs" is an arbitrary subdir name,
which works fine for such easy cases (#include )
But what about frameworks which want to use a namespace for their headers,
(#include ), like kjs and kio?
I
