C++/CLI generic constructor constraint

[Alon Fliess]

Hi

I am trying to write a generic class that instantiates the generic
type, but I can not find the correct way to give it the constructor
constraint.

For example:
In C#:

class X<T> where T:new()
{
static public T F() { return new T(); }
}

In C++/CLI:
generic<class T> where T:???? //(new(), gcnew() or what?
class X
{
public:
static T ^F() { return gcnew T(); }
};

[Carl Daniel [VC++ MVP]]

Alon Fliess wrote:

Hi

I am trying to write a generic class that instantiates the generic
type, but I can not find the correct way to give it the constructor
constraint.

For example:
In C#:

class X<T> where T:new()
{
static public T F() { return new T(); }
}

In C++/CLI:
generic<class T> where T:???? //(new(), gcnew() or what?
class X
{
public:
static T ^F() { return gcnew T(); }
};

IIUC, C++/CLI doesn't support authoring of generic constraints for the VC++
2005 release. It will honor generic constraints of generics authored in
another language (C#), however. As I understand it, the ECMA committee is
still working on syntax that will support generics but not collide with the
already complicated C++ type specifier syntax.

-cd

[Tomas Restrepo \(MVP\)]

Alon,

IIUC, C++/CLI doesn't support authoring of generic constraints for the
VC++ 2005 release. It will honor generic constraints of generics authored
in another language (C#), however. As I understand it, the ECMA committee
is still working on syntax that will support generics but not collide with
the already complicated C++ type specifier syntax.

Just to complement what Carl wrote, you can still do this in C++/CLI, but
you'll need reflection to create the object inside your generic. Here's an
example:
ref class A
{
public:
A() { Console::WriteL ine("In Constructor()") ; }
};

generic <class T>
ref class B
{
public:
T CreateT() {
return (T)Activator::C reateInstance(T ::typeid);
}
};
int main()
{
B<A^>^ b = gcnew B<A^>;
A^ a = b->CreateT();
}

--
Tomas Restrepo
to****@mvps.org
http://www.winterdom.com/weblog

[Alon Fliess]

"Tomas Restrepo \(MVP\)" <to****@mvps.or g> wrote in message news:<us******* *******@TK2MSFT NGP14.phx.gbl>. ..

Alon,

IIUC, C++/CLI doesn't support authoring of generic constraints for the
VC++ 2005 release. It will honor generic constraints of generics authored
in another language (C#), however. As I understand it, the ECMA committee
is still working on syntax that will support generics but not collide with
the already complicated C++ type specifier syntax.

Just to complement what Carl wrote, you can still do this in C++/CLI, but
you'll need reflection to create the object inside your generic. Here's an
example:
ref class A
{
public:
A() { Console::WriteL ine("In Constructor()") ; }
};

generic <class T>
ref class B
{
public:
T CreateT() {
return (T)Activator::C reateInstance(T ::typeid);
}
};
int main()
{
B<A^>^ b = gcnew B<A^>;
A^ a = b->CreateT();
}

Hi

This is funny, I wanted to compare a C++ based factory pattern with
the Activator mechanism, to find out the performance differences and
other pros/cons (type safety, etc.) And I get an answer that I can use
the activator....
I think that I will use a template to create the Factory, however
other languages will have to implement their concrete creator
(something that generic would have solved)

Alon.

[Tomas Restrepo \(MVP\)]

Hi Alon,

This is funny, I wanted to compare a C++ based factory pattern with
the Activator mechanism, to find out the performance differences and
other pros/cons (type safety, etc.) And I get an answer that I can use
the activator....

Well, the above *is* type safe, though it does use reflection which can
potentially be a little bit slower... however, that makes very little
difference in most cases, unless you're created a very large number of
objects in tight loops.
--
Tomas Restrepo
to****@mvps.org

[Alon Fliess]

"Tomas Restrepo \(MVP\)" <to****@mvps.or g> wrote in message news:<#k******* *******@TK2MSFT NGP09.phx.gbl>. ..

Hi Alon,

This is funny, I wanted to compare a C++ based factory pattern with
the Activator mechanism, to find out the performance differences and
other pros/cons (type safety, etc.) And I get an answer that I can use
the activator....

Well, the above *is* type safe, though it does use reflection which can
potentially be a little bit slower... however, that makes very little
difference in most cases, unless you're created a very large number of
objects in tight loops.

I agree with you about the type safeness, and the small performance
hit, but C++/CLI should be the strongest .Net language...

Generic constraint is a feature that C# does better (for now). I have
read that C++/CLI will support interface based constraint, and in the
ECMA draft there is a question about ctor constraint, so I'm not so
sure that they will not come up with some sort of constraint syntax
until the release.

Alon.

[Tomas Restrepo \(MVP\)]

Alon,

I agree with you about the type safeness, and the small performance
hit, but C++/CLI should be the strongest .Net language...

Generic constraint is a feature that C# does better (for now). I have
read that C++/CLI will support interface based constraint, and in the
ECMA draft there is a question about ctor constraint, so I'm not so
sure that they will not come up with some sort of constraint syntax
until the release.

It *does* support interface based constraints, just not the constructor
constraint. Here's an example:

#using <mscorlib.dll >

using namespace System;
using namespace System::Collect ions::Generic;
generic <typename T, typename V>
where T : IEnumerable<V>
ref class IWillEnumerateY ou
{
public:
void DoIt(T t)
{
for each ( V v in t )
{
Console::WriteL ine(v);
}
}
};

int main()
{
List<String^>^ stringList = gcnew List<String^>() ;
stringList->Add("String 1");
stringList->Add("String 2");
stringList->Add("String 3");
IWillEnumerateY ou<List<String^ >^, String^>^ en
= gcnew IWillEnumerateY ou<List<String^ >^, String^>();

en->DoIt(stringLis t);

}
--
Tomas Restrepo
to****@mvps.org
http://www.winterdom.com/

[Ioannis Vranos]

For anyone interested, this is the latest draft:
http://www.plumhall.com/C++-CLI%20draft%201.10.pdf
I think it is high time in msdn site, the outdated draft to be replaced with this.

[Alon Fliess]

Ioannis Vranos <iv*@remove.thi s.grad.com> wrote in message news:<#w******* *******@TK2MSFT NGP09.phx.gbl>. ..

For anyone interested, this is the latest draft:
http://www.plumhall.com/C++-CLI%20draft%201.10.pdf
I think it is high time in msdn site, the outdated draft to be replaced with this.

Thank you very much.

I will ask someone at Microsoft to update the MSDN link.

Alon.

[Ioannis Vranos]

Alon Fliess wrote:

Thank you very much.

I will ask someone at Microsoft to update the MSDN link.

To make things easier, you may continue finding the latest drafts in here:
http://www.plumhall.com/ecma/index.html