<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<blockquote cite="mid:55F86CBB.6030804@mi.fu-berlin.de" type="cite">
<blockquote type="cite">
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">No, we can't fix index_sequence in dune-common, because this
requires C++11, namely template aliases. The standard says,
that index_sequence<i> _is_ an interger_sequence<size_t,i>,
not derived, convertible, or anything else. But this can't
be achieved without template aliases.</pre>
</blockquote>
Yes, but we have template aliases in dune-common post-2.4, right?<br>
--<br>
Oliver<br>
<br>
<blockquote cite="mid:55F86CBB.6030804@mi.fu-berlin.de" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">The pre-made index objects now live in Dune::TypeTree::Indices (I thought the „Static“ was a little redundant).
I really like the idea of those constants and would like to see them in dune-common after the release of 2.4.
</pre>
</blockquote>
<pre wrap="">Seconded -- then I could use them for MultiTypeBlockVector.
Nitpicking: wouldn't constant_index be a better name than index_constant?
(I won't even try to enforce 'standard Dune' camelCase with you :-) )
</pre>
</blockquote>
<pre wrap="">My proposal 'index_constant' tried to stay in line with index_sequence
that also specializes some static index thingy for size_t. But t´since
it's not in the standard using IntergerConstant would also be fine.
Carsten
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
dune-functions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dune-functions@dune-project.org">dune-functions@dune-project.org</a>
<a class="moz-txt-link-freetext" href="http://lists.dune-project.org/mailman/listinfo/dune-functions">http://lists.dune-project.org/mailman/listinfo/dune-functions</a>
</pre>
</blockquote>
<br>
</body>
</html>