Nested name specifier help!

General JUCE discussion
1

i’m getting a nested name specifier error - but i’m flummoxed as to how to get to the bottom of the issue.

it occurs on this line: FileTypes::FileTypes() {

in this file:

------------------- FileTypes.cpp --------------------------

// ====== AttributeTest =======

#ifndef FILETYPES_HEADER
#define FILETYPES_HEADER

#include “AttributeTest.hpp”

BEGIN_RBF_NAMESPACE

//****************************************** FileTypes *******************************************

//-------------------------------------- FileTypes:: FileTypes --------------------------------------
FileTypes::FileTypes() {

}

END_RBF_NAMESPACE

#endif // FILETYPES_HEADER__

----------------------- End FileTypes.cpp---------------------------------

----------------- FileTypes.hpp -------------------------------------

// ====== AttributeTest =======

#ifndef FILETYPES_HEADER
#define FILETYPES_HEADER

#include “AttributeTest.hpp”

// — Includes for class dependencies —

class FileTypeCollection;

BEGIN_RBF_NAMESPACE

//****************************************** FileTypes *******************************************
class FileTypes : public FileTypeCollection
{

 public:
      FileTypes() ;


 protected:


 private:

      JUCE_LEAK_DETECTOR (FileTypes);

};

END_RBF_NAMESPACE

#endif // FILETYPES_HEADER__

-------------------------- IN FILE RBClasses.hpp --------------------------

class Filetype;

class FileTypeCollection : public OBJECT ESFT(FileTypeCollection)
{
public:

};

class Filetype : public OBJECT
{
public:
Filetype( STRING name, STRING DisplayName, STRING creator, STRING mactype, STRING extensions, REF(PictureJ) icon );
Filetype();

};

2

Remove half of the constructor and see if you still get the error. Iteratively reduce the code there until you find the line that causes the error to go away when removed.

3

That’s an… erm… unique… C++ coding style you’ve got going on there. :shock:

4

yep.

mea culpa. lots needs changing.
macros of course being just one of them. but first i just need to get past this giant humdinger and other finger trouble.

PLUS - bear in mind the code above was edited by me to show here. but the actual code is also attached.

The PROPERTY macros are there to simulate REALbasic/C# style properties - ie getters/setters

About time we had them built into the C++ language methinks.

C++ is only just beginning to catch up with what C# has been doing for ages. And thats even without any mention of managed ( yuk ) code…

5

thanks for the tip.

have now commented out all “interiors” and edited this in my original post contents here.

but i’m afraid no change… still the same error message on the same line.

any more hints ? i’m normally ok at this elimination game, but am just mentally blocked/stuck here at the mo’.