Message-Id: Comments: Authenticated sender is From: "Salvador Eduardo Tropea (SET)" Organization: INTI To: Sebastien BROCHET , djgpp AT delorie DOT com Date: Fri, 20 Mar 1998 14:13:45 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Limititation with DJGPP, scope problem ... In-reply-to: <3512731B.EA2518A1@geocities.com> Precedence: bulk Sebastien BROCHET wrote: > I think I've come into a limitation in the use of DJGPP. > Although this limitation can be avoided , hopefully !, it is still a bit > annoying. > [sniped example] > > This snippet compiles well with BC3.0/3.1 and watcom 10.x > I think the code above compiles well with DJGPP too but in my project > there are a few more classes with some dependencies ... > And DJGPP complains something like that : > "Lookup in the scope 'class A' does not match lookup in the current > scope" > in the line (*) : m_pA->Set(Value); // method B::Raise > > I can work around by writing : > int i = Value; > m_pA->Set(i); > > and it compiles well. I never experimented it. Can you post a piece of code where the problem *can* be reproduced. Because your example is OK and compiled OK. So perhaps your code isn't OK and that's why it doesn't compile OK ;-) (silly explanation, sorry). It can be some bug in gcc or some typo. SET ------------------------------------ 0 -------------------------------- Visit my home page: http://set-soft.home.ml.org/ or http://www.geocities.com/SiliconValley/Vista/6552/ Salvador Eduardo Tropea (SET). (Electronics Engineer) Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org CQ: 2951574 Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA TE: +(541) 759 0013