[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Tuesday 29 January 2008, AJ wrote:
> allefant wrote:
> > On Jan 29, 2008 1:56 PM, AJ <aj@xxxxxxxxxx> wrote:
> >> Has this situation been covered in future allegro designs?
> >> Is there a solution for this?
> >>
> >> If no solution is currently tabled, would it be appropriate to add
> >> ASSERT(sizeof(..)) anywhere potential for problems exists?
> >
> > Personally, I prefer this solution:
> >
> > Never ever use long. Use int when it's ok to have only 32-bit. Use
> > int32_t and int64_t where it matters.
>
> Agreed. Can we start looking at solutions for all instances of long ?
>
Don't see why not, but allegro works here on my amd64 box.
Just tried out the demo infact, and the only things I saw different than I
remembered was it saw my two monitors as one screen (I changed to xrandr
drivers vs Xinerama, someone needs to provide support for xrandr thats for
sure), and I don't ever remember being able to shoot more than one missle at
a time :o
--
Thomas Fjellstrom
tfjellstrom@xxxxxxxxxx