make this compile with gcc 3.4

we want to stay gcc 3.4 compliant, so folks please update your compilers

1 files changed, 2 insertions, 3 deletions

diff --git a/libopie2/opiepim/core/opimaccessfactory.h b/libopie2/opiepim/core/opimaccessfactory.h
index eecfa96..283b6ab 100644
--- a/libopie2/opiepim/core/opimaccessfactory.h
+++ b/libopie2/opiepim/core/opimaccessfactory.h
@@ -28,91 +28,90 @@
 */
 
 #ifndef __OPIE_OPIMACCESSFACTORY_H_
 #define __OPIE_OPIMACCESSFACTORY_H_
 
 #include <opie2/opimglobal.h>
 #include <opie2/obackendfactory.h>
 #include <opie2/ocontactaccess.h>
 #include <opie2/otodoaccess.h>
 #include <opie2/odatebookaccess.h>
 
 using namespace Opie::Pim;
 
 namespace Opie {
 
 
 /**
  * This class is our factory for creating PIM access objects. You should use these objects to load, store and search
  * information in our PIM databases. Currently we support objects for accessing the datebook, the contact- and the
  * todolist. 
  * @see OPimGlobal for more information of used values.
  *
  * This class - as the whole PIM Api - is making use of templates
  *
  * Example for getting an access object for the XML database of todolist:
  * <pre>
  *   OPimTodoAccess* access = OPimAccessFactory<OPimTodoAccess>::create( OPimGlobal::TODOLIST, OPimGlobal::XML, "example" );
  * </pre>
  *
  * @author Stefan Eilers
  * @version 0.1
  */
- */
 
 template<class T>
 class OPimAccessFactory
 {
  public: 
 
 	// Maybe we should introduce a global class for storing such global enums 
 	// (something like opimglobal.h) ? (eilers)
 
 	OPimAccessFactory() {};
 
 	/**
 	 * Returns the selected PIM access-object.
 	 * @param type Type of the selected database (addressbook, todolist or datebook)
 	 * @param dbStyle Which database style should be used (xml, sql, vcard)
 	 * @param appName "Name" of your application. This should be any constant string which is used
 	 *                by some backends for creating special files (i.e.journal files). Please keep the
 	 *                string unique for your application !
 	 * @see OPimGlobal
 	 */
 	static T* create( OPimGlobal::PimType type, OPimGlobal::DatabaseStyle dbStyle, const QString& appName ){
 
 		switch ( type ){
 		case OPimGlobal::TODOLIST:
 			return dynamic_cast<T*>( new OPimTodoAccess( OBackendFactory<OPimTodoAccessBackend>::create( type, dbStyle, appName ) ) );
 		case OPimGlobal::CONTACTLIST:
 			return dynamic_cast<T*>( new OPimContactAccess( QString::null, QString::null, OBackendFactory<OPimContactAccessBackend>::create( type, dbStyle, appName ) ) );
 		case OPimGlobal::DATEBOOK:
 			return dynamic_cast<T*>( new ODateBookAccess( OBackendFactory<ODateBookAccessBackend>::create( type, dbStyle, appName ) ) );
 		default:
 			return 0l;
 			
 		}
 	}
 
 
 	/**
 	 * Returns the selected PIM access-object, using the default database style
 	 * Which style is selected is defined in the configfile "pimaccess.conf" in 
 	 * the directory "Settings"
 	 * @param type Type of the selected database (addressbook, todolist or datebook)
 	 * @param appName "Name" of your application. This should be any constant string which is used
 	 *                by some backends for creating special files (i.e.journal files). Please keep the
 	 *                string unique for your application !
 	 * @see OPimGlobal
 	 * 
 	 */
-	static T* default( OPimGlobal::PimType type, const QString& appName ){
+	static T* default( typename OPimGlobal::PimType type, const QString& appName ){
 
-		return create( type, OPimGlobal::DEFAULT, appName )
+		return create( type, OPimGlobal::DEFAULT, appName );
 
 	}
 };
 
 }
 
 
 #endif