#163: Decide into what mln_?iter(T) should expand ---------------------------------+------------------------------------------ Reporter: levill_r | Owner: Olena Team Type: proposal | Status: new Priority: minor | Milestone: Olena 1.0 Component: Milena | Version: 1.0 Keywords: convention shortcut | ---------------------------------+------------------------------------------ In source:trunk/milena/mln/core/macros.hh, the macros
{{{ #!cpp mln_?iter(T) mln_?iter_(T) }}}
expand as
{{{ #!cpp typename T::fwd_?iter T::fwd_?iter }}}
Shouldn't they expand as
{{{ #!cpp typename T::?iter T::?iter }}}
?
#163: Decide how « mln_?iter(T) » macros should expand -----------------------+---------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: proposal | Status: new Priority: minor | Milestone: Olena 1.0 Component: Milena | Version: 1.0 Resolution: | Keywords: convention shortcut -----------------------+---------------------------------------------------- Changes (by levill_r):
* summary: Decide into what mln_?iter(T) should expand => Decide how « mln_?iter(T) » macros should expand
Old description:
In source:trunk/milena/mln/core/macros.hh, the macros
{{{ #!cpp mln_?iter(T) mln_?iter_(T) }}}
expand as
{{{ #!cpp typename T::fwd_?iter T::fwd_?iter }}}
Shouldn't they expand as
{{{ #!cpp typename T::?iter T::?iter }}}
?
New description:
In source:trunk/milena/mln/core/macros.hh, the macros
{{{ #!cpp mln_?iter(T) mln_?iter_(T) }}}
expand as
{{{ #!cpp typename T::fwd_?iter T::fwd_?iter }}}
Shouldn't they expand as
{{{ #!cpp typename T::?iter T::?iter }}}
?
If so, we should define `?iter` `typedefs` (defaulting to `fwd_?iter`) in relevant classes.
Comment:
Mention `?iter` `typedefs`.
#163: Decide how « mln_?iter(T) » macros should expand -----------------------+---------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: proposal | Status: new Priority: critical | Milestone: Olena 1.0 Component: Milena | Version: 1.0 Resolution: | Keywords: convention shortcut -----------------------+---------------------------------------------------- Changes (by levill_r):
* priority: minor => critical
Old description:
In source:trunk/milena/mln/core/macros.hh, the macros
{{{ #!cpp mln_?iter(T) mln_?iter_(T) }}}
expand as
{{{ #!cpp typename T::fwd_?iter T::fwd_?iter }}}
Shouldn't they expand as
{{{ #!cpp typename T::?iter T::?iter }}}
?
If so, we should define `?iter` `typedefs` (defaulting to `fwd_?iter`) in relevant classes.
New description:
In source:trunk/milena/mln/core/macros.hh, the macros
{{{ #!cpp mln_?iter(T) mln_?iter_(T) }}}
expand as
{{{ #!cpp typename T::fwd_?iter T::fwd_?iter }}}
Shouldn't they expand as
{{{ #!cpp typename T::?iter T::?iter }}}
?
This concerns (as of r3853) the following macros: {{{ #!cpp define mln_qiter(T) typename T::fwd_qiter define mln_qiter_(T) T::fwd_qiter define mln_niter(T) typename T::fwd_niter define mln_niter_(T) T::fwd_niter define mln_viter(T) typename T::fwd_viter define mln_viter_(T) T::fwd_viter }}}
If so, we should define `?iter` `typedefs` (defaulting to `fwd_?iter`) in relevant classes.
--
#163: Decide how « mln_?iter(T) » macros should expand -----------------------+---------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: proposal | Status: new Priority: critical | Milestone: Olena 1.1 Component: Milena | Version: 1.0 Resolution: | Keywords: convention shortcut -----------------------+---------------------------------------------------- Changes (by levill_r):
* milestone: Olena 1.0 => Olena 1.1
Comment:
Not required for [milestone:"Olena 1.0" Olena 1.0]; postponing to [milestone:"Olena 1.1" Olena 1.1].