This might have already been requested, but sometimes it is very convenient to add implementation/declaration stubs for yet undefined methods from the context of their usage.
For instance:
class Banana {public:};
class Person {public:};
...
void foo()
{
Person bob;
Banana banana;
// Right click over peel can suggest creating a stub for
// Person::peel(Banana & banana)
bob.peel(banana);
}
// Now Person class looks like this:
class Person {
public:
void peel(Banana & banana);
}
// The stub could also understand return values from context:
class PeeledBanana {
};
void foo()
{
Person bob;
Banana banana;
// Same as before, but return type is now PeeledBanana and not void.
PeeledBanana peeled = bob.peel(banana);
}
This allows writing code that uses functions before they are even defined and quickly create their implementation stubs on the fly.
Create stubs for unimplemented methods.
Posted - Mar 21 2009 : 08:46:07 AM
