C / C++ / MFC

#include <cstring>
#include <string>
#include <iostream>


using namespace std;



int main()
{
    int data2;
    char buff[1024];
    unsigned int value;
    int charsRead; 

    char selection;
    cout << "A) Complete  B) Partial  C) UNKNOWN" << endl;
    cin >> selection;



    bool validEntry = false;
	while (!validEntry)
	{ 
		cout << "Please enter the number of subunits: ";
		cin.getline(buff, 1023, '\n');

		if (sscanf(buff, "%u%n",&value,&charsRead)==1 && value >=1 && value <= 12)
		   validEntry = true;
	}

	data2 = value;

  return 0;

}

toxcct wrote:

pthread is a header you wrote

mehmetned wrote:

why was this error produced?

"The largest fire starts but with the smallest spark." - David Crow

"Judge not by the eye but by the heart." - Native American Proverb

Christian Graus wrote:

But a class *is* a struct.

Dave Schumann wrote:

So why can't B - which IS AN A - access the value member of another A?

"The largest fire starts but with the smallest spark." - David Crow

"Judge not by the eye but by the heart." - Native American Proverb

Maximilien wrote:

all members in structs should be public

Dave Schumann wrote:

No it's not.

Dave Schumann wrote:

Changing these to "classes" with public: at the beginning has no effect (I've tried it)

struct A
{
    A* partner;
 
    void doodah()
    { ++partner->value; } //this is legal
    int value; 
};

class A
{
public:
    A* partner;
 
    void doodah()
    { ++partner->value; } //this is legal
    int value;
};

"The largest fire starts but with the smallest spark." - David Crow

"Judge not by the eye but by the heart." - Native American Proverb

Dave Schumann wrote:

I declared "protected:" for a reason, not because I like having things not compile. This is a toy version of a much larger problem. I can't stand posters who post 20 pages of code so I figured I'd boil the issue down. In fact in my case the issue is accessing a *function*...and there's virtual stuff and blah blah blah. Now you're getting bored, appropriately. None of that is relevant to the compiler error which I can't understand.

Zac Howland wrote:

I will only mention that almost always, protected should be replaced by private.

toxcct wrote:

maybe, but here, the protected member is accessed by a children... so, putting it private will cause a new problem in his code.