RE: [AD] #include <allegro.h> vs #include "allegro.h" in the examples

["Robert Ohannessian" <ROhannessian@xxxxxxxxxx>]

I think the reason was that the examples get built before Allegro is
installed, so the compiler may not find allegro.h if you use <>.

> -----Original Message-----
> From: alleg-developers-admin@xxxxxxxxxx [mailto:alleg-
> developers-admin@xxxxxxxxxx] On Behalf Of Elias Pschernig
> Sent: Sunday, October 03, 2004 4:36 AM
> To: alleg-developers
> Subject: [AD] #include <allegro.h> vs #include "allegro.h" in the
examples
> 
> Does anyone know the reason for using "" in the examples? This makes
gcc
> search in the current directory first - which is kind of pointless.
But
> it also doesn't hurt. Still, in my own programs, I always use #include
> <allegro.h>, so maybe we should modify the examples to use the same.
Or
> was there another reason for the ""?
> 
> 
> --
> Elias Pschernig
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on
ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give
us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
> more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers