Re: [AD] Location of allegro.log file (4.3.10)

[Grzegorz Adam Hankiewicz <gradha@xxxxxxxxxx>]

El 01/10/2008, a las 7:10, Colin Ward escribió:
> Oh I could certainly just change src/allegro.c so that it said
> "RAM:allegro.log" rather than just "allegro.log" but then that is an  
> Amiga
> specific change that is only on my hard drive.  Ultimately the  
> source will
> go into Subversion so the change should apply to anyone who gets the  
> source
> and builds it, hence the need for a macro such as #define  
> ALLEGRO_LOG_FILE
> "RAM:allegro.log" that is used.  Or am I misunderstanding you?

You seemed to be seeking for advice on whether doing such a change was  
ok or not, and from you reports it seems to be the sanest option  
(though I would take care in not expanding the log's limited scope  
with feature creep while you are at it).

With regards to the implementation, it can be a define, it can be a  
runtime function. You are developing it, so you make the choice based  
on what you think is better. A #define looks right for the beginning.