Review Request 122169: Use oldcpp behavior when inserting include paths.

[Sergey Kalinichev]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122169/#review74477
-----------------------------------------------------------



codecompletion/includepathcompletioncontext.cpp
<https://git.reviewboard.kde.org/r/122169/#comment51657>

    Here: https://git.reviewboard.kde.org/r/120241/
    were mentioned that "#   include" is valid too. I think that we still should support it.



codecompletion/includepathcompletioncontext.cpp
<https://git.reviewboard.kde.org/r/122169/#comment51658>

    Actually I don't like how oldcpp removes the whole line, including comments. I think that we shouldn't remove anything after closing " or >


- Sergey Kalinichev


On Jan. 20, 2015, 4:51 p.m., Milian Wolff wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/122169/
> -----------------------------------------------------------
> 
> (Updated Jan. 20, 2015, 4:51 p.m.)
> 
> 
> Review request for KDevelop.
> 
> 
> Repository: kdev-clang
> 
> 
> Description
> -------
> 
> This is much better, in my opinion. It allows one to easily include
> long paths as well as change existing includes more easily as the
> rest of the line gets removed as well.
> 
> 
> Diffs
> -----
> 
>   codecompletion/includepathcompletioncontext.cpp 9dea2879418c4f81ab1927d848c831b092bd11e6 
> 
> Diff: https://git.reviewboard.kde.org/r/122169/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Milian Wolff
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20150121/81e55184/attachment.html>