How to initialize a private static const array of a private child class in a class?

I've been working on my homework project and now I am to declare a class:

Code:

#define PIECE_SIZE 5
#define PIECE_NUM 2
#include <vector>
class Piece
{
	class InternalPiece
	{
		std::vector<bool> Array;
		
		public:
		InternalPiece(const bool a[])
		{
			for (int i = 0; i < PIECE_SIZE * PIECE_SIZE; ++i)
				Array[i] = a[i];
		}
		bool operator()(const int &x, const int &y) const
		{
			return (bool)Array[x * PIECE_SIZE + y];
		}
	};
	public:
	static const InternalPiece pieces[];

And now how am I to initialize the array `pieces'? Initialize it within the class definition is unavailable:

Code:

error: expected constructor, destructor, or type conversion before ‘=’ token

And so is to initialize when you have a Piece object, since the class InternalPiece is private:

Code:

error: ‘class Piece::InternalPiece’ is private

Anyone knows how to solve this? Great thanks.

Code:

//declaration
static const InternalPiece pieces[];


//definition in global scope
const Piece::InternalPiece Piece::pieces[N] = {true, true};

This doesn't work since:

1. InternalPiece variables are constructed from a bool array.
2. The class InternalPiece is private hence we cannot call the constructor outside the class Piece definition.

Originally Posted by jinhao

Code:

//declaration
static const InternalPiece pieces[];


//definition in global scope
const Piece::InternalPiece Piece::pieces[N] = {true, true};

Since InternalPiece is private, why is it being exposed to the public via the pieces member variable? This consideration aside, I can suggest that you provide a default constructor, and then write in a source file:

Code:

const Piece::InternalPiece Piece::pieces[PIECE_NUM];

Incidentally, change PIECE_SIZE and PIECE_NUM from macros to static const integer member variables of Piece, or possibly an enum in Piece.

Originally Posted by ryanli

# The class InternalPiece is private hence we cannot call the constructor outside the class Piece definition.

That is true, but by correctly qualifying the static member's name, one can initialise it outside of the definition of the class.