| Re: [AD] Don't use Devpaks |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: allegro-developers@xxxxxxxxxx
- Subject: Re: [AD] Don't use Devpaks
- From: Thomas Fjellstrom <thomas@xxxxxxxxxx>
- Date: Mon, 09 May 2016 14:05:31 -0600
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=fjellstrom.ca; s=mail; t=1462824332; bh=Zug/2IFWOqhGxZNK57uGckrIxfhuo/OWRDMN4pBRQ2g=; h=From:To:Reply-To:Subject:Date:In-Reply-To:References:From; b=JogarXFuWdGzt7snWQZ8yA8XrcQ0ieNu+FaMzS20x8nmQ68RWGl48aOtALbcdJ9ql augJLaw+Wg7DEjKuRN6YEZxw+4TqV/LQSc6JrqCmkonPGpEgyEiXURmXQLCiMN02Xy X4ayTtrA1PO1lnz6WxAL1AP9mXa3BYPRpv2QhmmQ=
On Mon 09 May 2016 10:51:19 AM Andrew Robinson wrote:
> >> I suppose all I want to know for a fact is, are the Allegro 5 APIs
> >> written
> >> in C++ or C?
> >
> >C, just like Allegro 4. But it is useable in C++.
>
> Phew! What a relief! C can be interfaced to any language, whereas C++ is
> compiler dependent due to THISCALL and name mangling being compiler
> dependent.
You don't really want to mix mingw and msvc compiled C libs either though.
>
> _______________________________________________
> Allegro-developers mailing list
> Allegro-developers@xxxxxxxxxx
> https://mail.gna.org/listinfo/allegro-developers
--
Thomas Fjellstrom
thomas@xxxxxxxxxx