Boost C++ Libraries: Ticket #6891: Add extension point to define how expressions are created from operators https://svn.boost.org/trac10/ticket/6891 <p> As discussed here: &lt;<a class="ext-link" href="http://lists.boost.org/proto/2012/05/0637.php"><span class="icon">​</span>http://lists.boost.org/proto/2012/05/0637.php</a>&gt; </p> <p> It would be nice to add a mechanism to allow to define what the operator overloads created by Proto will do. Unlike other functions where a Proto-based library can construct nodes the way it wishes, there is no control and what the built-in C++ operators do. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/6891 Trac 1.4.3 Eric Niebler Tue, 05 Jun 2012 18:45:50 GMT status changed https://svn.boost.org/trac10/ticket/6891#comment:1 https://svn.boost.org/trac10/ticket/6891#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">assigned</span> </li> </ul> <p> I'm keeping this feature request in mind while designing proto-11. In the current design, users will be have a per-domain <code></code><code>make_expr</code><code></code> customization point. I foresee all of proto's operator overloads going through this customization point. So, if for your domain, your <code></code><code>make_expr</code><code></code> turns <code></code><code>tag::foo</code><code></code> into <code></code><code>my_tag&lt;tag::foo&gt;</code><code></code> (for instance), that would just work. </p> <p> Does this address your scenario? </p> Ticket Mathias Gaunard Wed, 06 Jun 2012 15:15:23 GMT <link>https://svn.boost.org/trac10/ticket/6891#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/6891#comment:2</guid> <description> <p> Hmm not quite what I needed. I only wanted the proto-provided operator overloads to call a customization point, not all calls to make_expr. </p> <p> But if we're talking about a complete redesign where generators disappear, I don't know how it is going to fit in the grander scheme of things. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Eric Niebler</dc:creator> <pubDate>Wed, 06 Jun 2012 17:39:53 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/6891#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/6891#comment:3</guid> <description> <p> I would object to a customization point that is only used by the operator overloads. I would like the behavior of the operator overloads to be easily explainable. Having it correspond to the behavior of <code></code><code>make_expr</code><code></code> feels right to me. </p> </description> <category>Ticket</category> </item> </channel> </rss>