Re: More ObjC++ work on @encode in C++ templates

["Nicola Pero" <nicola dot pero at meta-innovation dot com>]

> In general, please try and avoid collisions on the testcase names with those names 
> from llvm-gcc-4.2...  If they have an encode-10.mm testcase, but not an encode-15, 
> go for encode-15.  The reason is that once we are done with the basics, one can 
> then see which testcases are in that tree to see what features and functionalities 
> we are still missing.  We may well have to reimplement the feature, but at least 
> we can have a quick pointer to what we are missing.

Sure.

Alternatively, maybe we should add new testcases (that we're not backporting from
the apple/trunk branch) to a new directory ?  Then we would never have an issue with 
conflicts. :-)

I think IainS was reorganizing the ObjC/ObjC++ testcases, maybe he has a recommendation
of where to add new testcases ?

Thanks