|
|
|
| Allegro 4.2.0 has been released! |
|
Matthew Leverton
Supreme Loser
January 1999
 |
Quote: It still gets 10 warnings, should I ignore them? Look for the project option to disable 64-bit compatibility warnings. Quote: Matthew, how come your static release lib is bigger than your static debug lib? I'm doing nothing but standard builds. In MSVC >= 7, they are all bigger than debug versions for me. Quote: Well, assuming I'm not wrong, you'll have to wait for the make files to get fixed before this happens. How so? I built static profiles for MSVC 6/7.0/7.1/8.0. |
|
Neil Walker
Member #210
April 2000
 |
I meant debugged profile. but thinking about it, I guess that doesn't make sense Neil. Neil. wii:0356-1384-6687-2022, kart:3308-4806-6002. XBOX:chucklepie |
|
kentl
Member #2,905
November 2002
|
Quote: Look for the project option to disable 64-bit compatibility warnings. Does this mean that Allegro has compatibility issues with 64-bit CPU's? Could something bad happen to 64-bit users, or is it just if you specifically compile for the 64-bit platform? |
|
Evert
Member #794
November 2000
 |
Quote: Does this mean that Allegro has compatibility issues with 64-bit CPU's? Not precisely. Allegro works fine in 64 bit mode in Linux, but the Windows port is 32 bit only for now. Part of the reason is lack of a 64 bit version of MinGW and disagreement between MSVC and GCC when it comes to the size of long integers. Lack of dedicated Windows developers also doesn't help, I'm sure. Quote: Could something bad happen to 64-bit users, or is it just if you specifically compile for the 64-bit platform? Chances are some things do not work correctly if Allegro were compiled as a 64 bit library in Windows. Using the 32 bit library is fine. |
|
kentl
Member #2,905
November 2002
|
Quote: Lack of dedicated Windows developers also doesn't help, I'm sure. That's bad, I would help out if I had the relevant knowledge, and some more time on my hands. I guess knowing Win32 API pretty well and especially DirectX is necessary though? Quote: Part of the reason is lack of a 64 bit version of MinGW and disagreement between MSVC and GCC when it comes to the size of long integers.
Not a good thing at all. Quote: Using the 32 bit library is fine.
Fine with me! |
|
Evert
Member #794
November 2000
|
Quote: That's bad, I would help out if I had the relevant knowledge, and some more time on my hands. I guess knowing Win32 API pretty well and especially DirectX is necessary though?
Well, someone who is a regular Windows user would be the most important, I think. There are a few on the mailinglist, but it seems that we still don't have a `full-time' Windows maintainer. Quote: Well Microsoft has never been about portable standards, I guess it's in their intrest to tie people with their OS as much as possible.
It isn't really Microsft's fault though. The C standard says almost nothing about the size of integer datatypes and it certainly doesn't say all compilers should have the same size for them. Anyway, we'll have to find a way to handle the problem eventually. |
|
kentl
Member #2,905
November 2002
|
Lets hope that someone steps up and helps you out. I won't though as I would make a false promise almost certainly (to much going on right now). |
|
Rogerio Penchel
Member #6,579
November 2005
|
The function reakey() is returning 0, when press alt-xxx (numeric pad), this was perfect in version 4.0.3 Platform: Windows This compiler I used to compiler Allegro 4.2.0 and the program with readkey() function. Thanks. |
|
Elias
Member #358
May 2000
|
Yes, seems this was an undocumented feature of 4.0.x. You might be able to simulate it with keyboard_callback. -- |
|
Evert
Member #794
November 2000
|
Undocumented or not, we should probably document this change in the API differences section. |
|
Thomas Harte
Member #33
April 2000
 |
Will the deprecated functions be removed from the next release? If not, would you accept a patch, as yet unwritten, that replaced the current generic compiler warnings with something more useful (e.g. function A is deprecated in favour of function B)? [My site] [Tetrominoes] |
|
Peter Wang
Member #23
April 2000
|
Quote: If not, would you accept a patch, as yet unwritten, that replaced the current generic compiler warnings with something more useful (e.g. function A is deprecated in favour of function B)? Absolutely.
|
|
Thomas Harte
Member #33
April 2000
|
Okay, but just one quick question - while the GCC builds generate their warnings in response to the _attribute_ ((deprecated)) stuff around line 130 in alconfig.h, where are MSVC, etc, getting their definitions of AL_FUNC_DEPRECATED, AL_PRINTFUNC_DEPRECATED and AL_INLINE_DEPRECATED? I can't seem to find anything in include/platform/* or anywhere else. [My site] [Tetrominoes] |
|
Peter Wang
Member #23
April 2000
|
Further down in alconfig.h (around line 218) there are fallbacks for non-gcc.
|
|
|
|
Well Microsoft has never been about portable standards, I guess it's in their intrest to tie people with their OS as much as possible.
