Download Conejo User's Manual

A Tour of Malibu
Category
Ethernet
Purpose
Provide software interface to ethernet-equipped DSP baseboards, such as the SBC6713e.
Provision for peripheral initialization and TCP/IP communications between target DSP and
Host PC.
Implemented within the Ethernet_Mb project.
Malibu uses C++ name spaces to distinguish its classes and methods from those of other libraries. The majority of the classes
within Malibu reside within the Innovative name space. Another common name space is OpenWire for classes that
make up the OpenWire data transfer and connection library in Malibu. There are other name spaces in Malibu that are used
internally and not usually involved at the application level.
Like any C++ library, to use Malibu objects you must include the appropriate header that defines the structure of the object
and its methods. If this object is in a namespace, the class name has to include the namespace to provide the full name of the
class. For instance:
#include <Quadia.h>
...
MyClass::DoWork()
{
Innovative::Quadia Dsp;
Dsp.Target(0);
Dsp.Open().
...
}
Since Quadia is in the Innovative namespace, its fully qualified name is Innovative::Quadia. To avoid having to
include the namespace, a using directive can be used to tell the compiler to search the Innovative namespace
automatically:
#include <Quadia.h>
using namespace Innovative;
...
MyClass::DoWork()
{
Quadia Dsp;
Dsp.Target(0);
Dsp.Open().
...
}
These directives should be used with caution, since names shared in two namespaces may create errors in compilation. Also,
be aware that it is poor form to employ the using namespace directive within a header file.
Refer to the Malibu.chm on-line help file for detailed descriptions of any of the classes or components in the Malibu library
suite.
Utility Classes
In order to provide the main services of the Malibu library, a number of building-block classes and methods were developed.
Many of these classes have uses in the user application as well as in the library.
Conejo User's Manual
24