cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/2003/03/04/11:01:47

From: "Joel_S" <jbs30000 DOT news DOT invalid AT web2news DOT net>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Vesa 2.0
Date: Tue, 04 Mar 2003 16:48:33 +0100
Organization: Web2news.com
Message-ID: <17593N913@web2news.com>
References: <17326N022 AT web2news DOT com> <Xns9333C01A96E16asu1cornelledu AT 132 DOT 236 DOT 56 DOT 8> <17482N497 AT web2news DOT com> <Xns9333E7234487Dasu1cornelledu AT 132 DOT 236 DOT 56 DOT 8> <17488N404 AT web2news DOT com> <3E6454E3 DOT D29B507C AT yahoo DOT com> <17545N461 AT web2news DOT com> <b42ctn$4il$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
MIME-Version: 1.0
NNTP-Posting-Host: 198.81.26.238
X-Complaints-To: abuse AT web2news DOT net
Lines: 21
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> Joel_S <jbs30000 DOT news DOT invalid AT web2news DOT net> wrote:
>> Problem solved, I simply changed
>> vesa_pm_info = malloc(r.x.cx);
>> to
>> vesa_pm_info = ( VESA_PM_INFO *)malloc(r.x.cx);
>
> Problem not solved, but avoided. 
>
> If that particular change made the code compile, that
> definitely means
> you're compiling it as C++, not C.  You never showed us an actual
> compilation command line, so it's hard to say how that happened.  But
> happen it did.  If forced to bet, I'd place my money on capital C
> vs. lower-case C.
I'm using RHIDE to build my programs with, not the command line.  I'm
using small case c for my files, but I'll try upper case to see what
happens.

-- 
Direct access to this group with http://web2news.com
http://web2news.com/?comp.os.msdos.djgpp

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019