Noob question on adding function boiler plate comment

[cmattb]

I would like to write a script that takes a function and automatically adds boiler plate comments e.g.

User writes the following function

int foo(int bar)
{
   return(bar+1);
}

Then user selects the text "int foo(int bar)" in the editor and runs the script such that the text becomes

/*********
* function: foo <short description>
* args: int bar <description>
* returns <description>
* <long description>
**********/
int foo(int bar)
{
   return(bar+1);
}

Many apologies if this has been done already - but I could not find a reference to such functionality in the forumns.

Any hints/suggestions would be very much appreciated

[cmattb]

So after going through the information on scripting I realised that it was not possible to do this in the script as there was only GetText and SetText available in the cbEditor class.

Therefore I have gone through (the slightly larger than expected) pain of writing the plugin in C++ code. I have the basics working but still have some generalisation work to do. Given the lack of responses from anyone else here I assume that this feature is not widely required from the community. 

However, I would like to request (and I expect I'm posting in the wrong place) that the script API of cbEditor is extended a little further to include reading calls like GetCurrentPos(), GetSelectionStart(), GetSelectionEnd(), etc and writing calls like ReplaceSelection(), etc.

There may well be a very good philisophical reason why this is not done currently, in which case you can continue to ignore this post 

[dmoore]

I suspect the only reason it hasn't been done is because noone has needed to do it until now. It wouldn't be too difficult add those extra functions to the exposed API, even for someone unfamiliar with C::B (just use the already exposed functions as templates)

EDIT: I guess there could be an issue with API/ABI stability, but just adding new functions shouldn't break old code. I doubt API/ABI stability is the key concern.

[MortenMacFly]

I doubt API/ABI stability is the key concern.

I'd say not anymore. ;-)