Oh no. My mentor JonCruz told me that adding virtual functions in c++ way might break things as c has fixed addresses and all, and so making virtual functions(dynamic allocation) might infict a blow on the those current functionalities.

On Fri, Jul 2, 2010 at 3:41 AM, <J.B.C.Engelen@...1656...578...> wrote:
> -----Original Message-----
> From: Abhishek Sharma [mailto:spyzer.abhishek0@...400...]
> Sent: 29 June 2010 20:19
>
> Hello all inkscape developers and users,
>
> I am currently developing the project named "C++ifying the SP Layer
and
> XML node privatization". I had been doing the development for the same
> for about a month now and have created a branch for the corresponding
> developed code. The code as of now c++ifies sp-item.h/cpp , sp-
> line.h/cpp, sp-polyline.h/.cpp and marks the beginning of
> document.h/.cpp . There are some performance increase but they shall
> become more noticeable when I attack the major parent classes like
> SPDekstop, SPDocument(SPItem already done, took me 2 weeks). The
branch
> is uploaded here
> https://code.launchpad.net/~spyzer-abhishek0/+junk/gsoc-cppify
>
> I shall be glad to have responses about the work from the developers.
> I shall soon be beginning the XML node privatization as well where the
> main job would be to highlight the areas where XML tree should be
> targeted to begin its purging.

Hi Abishek,

Great work! I hope you were able to script a lot of the work.
I see you still have the SPItemClass class next to SPItem, for the
C-like 'virtual' functions. Are you planning on making those functions
real virtual functions of the SPItem class?

Ciao,
 Johan



--
Abhishek Sharma
B-Tech Information Technology
Indian Institute of Information Technology(Amethi Campus)