On Thursday, March 28, 2002, at 06:12 AM, David Megginson wrote:
Jonathan Polley writes:
.\src\Input/input.hxx(321) : error C2248: 'MAX_MOUSE_BUTTONS' : cannot
access private enumerator declared in class 'FGInput'
.\src\Input/input.hxx(250) : see declaration of
Doh! I just had a thought. Could MSVC be having a problem because the
enum containing MAX_MOUSE_BUTTONS is *private* rather than public? I have
seen some compilers apply different rules to private vs. public data in
that they take an 'ignorance is bliss' approach to private data (i.e.,
Jonathan Polley writes:
This brings about the philosophical question, Is is possible to work
around ALL MSVC bugs?
I'm pretty sure that people are successfully building FlightGear
already with MSVC 6.
I also don't like the name space problems that #defines cause, especially
when it
Jonathan Polley wrote:
On Thursday, March 28, 2002, at 06:12 AM, David Megginson wrote:
Jonathan Polley writes:
.\src\Input/input.hxx(321) : error C2248: 'MAX_MOUSE_BUTTONS' : cannot
access private enumerator declared in class 'FGInput'
.\src\Input/input.hxx(250) : see
Its ALIVE!!!
I reverted input.hxx back to what was in CVS and moved the enumeration
from being private to public and MSVC now likes using an enumeration
element to define an array. Why the compiler cares about an enum being
private vs. public, I will never know (although I have seen this
Jonathan Polley writes:
I reverted input.hxx back to what was in CVS and moved the enumeration
from being private to public and MSVC now likes using an enumeration
element to define an array. Why the compiler cares about an enum being
private vs. public, I will never know (although I
On Thursday, March 28, 2002, at 04:14 PM, David Megginson wrote:
Does it still work if the enum is protected? I'd like to keep things
as well encapsulated as possible.
*trundles downstairs to PC*
*makes edit*
*compiles*
*says dirty words*
*trundles back upstairs to Mac*
MSVC gives a
David Megginson wrote:
Jonathan Polley writes:
I reverted input.hxx back to what was in CVS and moved the enumeration
from being private to public and MSVC now likes using an enumeration
element to define an array. Why the compiler cares about an enum being
private vs. public, I
Jonathan Polley wrote:
*trundles downstairs to PC*
*makes edit*
*compiles*
*says dirty words*
*trundles back upstairs to Mac*
*ssh's into home machine from 7 miles away at work*
*sips coke*
*cvs update's FlightGear source*
*compiles*
*makes edit*
*debugs*
*sticks out toungue*
*decides
Bernie,
I just made your change and now input.cxx compiles fine.
/**
* Settings for a mouse.
*/
struct mouse; // This is new code
friend struct mouse; // This is new code
struct mouse {
mouse ();
virtual ~mouse ();
int x;
int y;
*connects to http://www.uk.research.att.com/vnc/ and downloads VNC for the
PC and Mac*
*installs VNC in both computers*
Buys the second license to the appropriate version of Windows
*does the 'happy dance'*
... it's the Microsoft tax dance.
Every computer that runs, or remotely controls,
Jonathan Polley wrote:
I am getting closer. I was able to resolve the link-time errors (added
a slew of new files to the MSVC project) and got an executable! There
was one build problem in that MSVC did not like an enumeration being
used to define the size of an array:
12 matches
Mail list logo
