RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

Coding Convention Question

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.
Coding Convention Question Eric Grivel 22 Jan 00:05
  Coding Convention Question Sven Neumann 22 Jan 14:01
Eric Grivel
2011-01-22 00:05:25 UTC (almost 14 years ago)

Coding Convention Question

Hi,

I'm looking at bug #596410 and in order to get to the import source in gimpimage.c, I seem to have to #include "../file/gimp-file.h" (to get to the GIMP_FILE_IMPORT_SOURCE_KEY constant). Is it appropriate to include a header file from a sibling directory this way?

Thanks, Eric

Sven Neumann
2011-01-22 14:01:17 UTC (almost 14 years ago)

Coding Convention Question

On Fri, 2011-01-21 at 19:05 -0500, Eric Grivel wrote:

Hi,

I'm looking at bug #596410 and in order to get to the import source in gimpimage.c, I seem to have to #include "../file/gimp-file.h" (to get to the GIMP_FILE_IMPORT_SOURCE_KEY constant). Is it appropriate to include a header file from a sibling directory this way?

No, you just #include "file/gimp-file.h". The include paths for the compiler are configured so that this will work.

Sven