It follows then that the EC++ definition is the interface by which application designers can access the parallel additions to C++ which Europa aims to supply, and these language extensions must be defined in such a way as to interface with standard (ANSI) C++. It shows how the Data Parallel libraries can be written in terms of the EC++ definition, although they need not be. Previous work undertaken in the field of Data Parallel C++ Research has shown that this parallelism can be expressed without changing C++ syntax, using class libraries written in standard C++. An example of this is the DPC++ project [Gilbert 94]. EC++ however, does not see a need to insist on this as long as these libraries have an EC++ interface which is accessible to the applications programmer. This then allows that the implementation of this section is left entirely to the compiler writer - and it can be implemented in EC++ or C++, where the C++ constructs used can be specific to a particular hardware architecture.