🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.linux.x
Article #235

Re: parse error when compile?

#235
From: John Darrington
Date: Tue, 29 Sep 1998 00:00
19 lines
1433 bytes
Seg Fault wrote:
> 
> > When I was trying to compile the following code, I always got the
> > parsing error at line 32 before * .
> >
> > I cannot find the error. Please tell me what's the normal cause of
> > the parsing error?
> 
> >       XRecordRange *rcRange[];  /* <=== parse error here before * . */
> 
> When I see this kind of error in C++ the cause is usually that the
> compiler does not know about the class. In this case, I would
> ensure that type XRecordRange is declared and/or is not some macro.
> 
> HTH,
> 
> Anthony
But he is not using C++.  I would suggest that he moves the declaration
of rcRange to the top of main.
Technical Details
Message-ID: <3610C1FF.BDEE4D48@elvis.murdoch.edu.au>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <36102de8.0@ruby.hknet.com> <3610397D.7E9E9771@ulster.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 11318c,8fe7b01c96b459ae
X-Google-Attributes: gid11318c,public
X-Google-Thread: f4bda,8fe7b01c96b459ae
X-Google-Attributes: gidf4bda,public
X-Google-Thread: 11038b,8fe7b01c96b459ae
X-Google-Attributes: gid11038b,public
From: John Darrington <j.darrington@elvis.murdoch.edu.au>
Subject: Re: parse error when compile?
Date: 1998/09/29
Message-ID: <3610C1FF.BDEE4D48@elvis.murdoch.edu.au>
X-Deja-AN: 395943184
Content-Transfer-Encoding: 7bit
References: <36102de8.0@ruby.hknet.com> <3610397D.7E9E9771@ulster.net>
Content-Type: text/plain; charset=us-ascii
Organization: Customer of Connect.com.au P/L, Perth, Australia
Mime-Version: 1.0
Newsgroups: comp.os.linux.x,comp.windows.x.intrinsics,gnu.gcc.help