Re: [Development] Coding convention for private includes

2017-01-23 Thread Thiago Macieira
On segunda-feira, 23 de janeiro de 2017 11:00:02 PST Kevin Ottens wrote: > > You need to be careful when including a private header from another > > private > > header. But if it's from a .cpp, you can use even relative paths. > > What do you have in mind as risk when you say one needs to be caref

Re: [Development] Coding convention for private includes

2017-01-23 Thread Kevin Ottens
Hello, On Friday, 20 January 2017 15:06:53 CET Thiago Macieira wrote: > On sexta-feira, 20 de janeiro de 2017 14:55:00 PST Sean Harmer wrote: > > Just a query about the coding convention around inclusion of private > > headers as specified at: > > > > https://wiki.qt.io/Coding_Conventions#Includi

Re: [Development] Coding convention for private includes

2017-01-20 Thread Thiago Macieira
On sexta-feira, 20 de janeiro de 2017 14:55:00 PST Sean Harmer wrote: > Hi, > > Just a query about the coding convention around inclusion of private headers > as specified at: > > https://wiki.qt.io/Coding_Conventions#Including_headers > > It states: > > If you need to include private headers,

[Development] Coding convention for private includes

2017-01-20 Thread Sean Harmer
Hi, Just a query about the coding convention around inclusion of private headers as specified at: https://wiki.qt.io/Coding_Conventions#Including_headers It states: If you need to include private headers, be careful. Use the following syntax, irrespective of which module or directory whatever