Re: request: add const member function flag for C++
Eric Ludlam <[email protected]>
| Newsgroups | gmane.emacs.cedet |
|---|---|
| Message-ID | <[email protected]> |
On 09/24/2014 07:21 AM, Oleh wrote:
> Hi Eric,
>
> Thanks for the patch. The recursive template parameters work for this case.
> I'll keep using it to see if any problems come up in more complex cases.
>
>>> #include<vector>
>>>
>>> template<int dim>
>>> class Point
>>> {
>>> };
>>>
>>> class ABC
>>> {
>>> template<int dim> bool test(std::vector<Point<dim> > x);
>>> };
>>>
> However, while the "dim" in "std::vector<Point<dim> >" is correctly
> parsed, the "dim" in "template<int dim>" isn't parsed.
> Instead this is produced:
>
> ("test" function
> (:template
> (("int" type nil nil nil))
> :type "bool" :arguments
> ...)
>
> while I would expect something like this:
>
> ("test" function
> (:template
> (("dim" variable (:type ("int" type nil nil nil))))
> :type "bool" :arguments
> ...)
>
> i.e. template arguments should be parsed similar to :arguments of a function.
>
Hi Oleh,
I've submitted a patch for the previous thing you emailed me, and to add
the extra detail of "dim" into the template tags that you note above.
I did not change the template value from a TYPE tag to a VARIABLE tag
because the current completion engine depends on the original
structure. Instead I just put a :varname into the type so it is there.
David Engster did most of the template handling in the smart completion
engine. Changing things around a bit would be something he'd have
better advice on.
Eric
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk