CV flag for being a method

[leonerd]

Given #2, it seems likely that a method will continue to be a CV much like a sub is. It would be useful for it to have a flag to indicate that it is a full method, as opposed to a simple unattached sub.

A good name for this would be CVf_METHOD, with associated macros CvMETHOD, CvMETHOD_on and CvMETHOD_off. However, there already exists a flag of that name, which is associated with the :method attribute and quiets certain parse-time warnings about ambiguous names.

[yuki-kimoto]

No problem to add the flag whether the CV is a method.

[Lamprecht]

Would this allow to croak if a method is called as sub and vice versa?
So that these would croak in class.t:

    is(Test1::hello(), "hello, world", 'Meth called as Function');
    is(Test2->NotAMethod(), "OK", 'Sub called as a method');

[leonerd]

Yes and no. Attempting to invoke a method as a plain function already fails, because of the $self check.

We can't (and probably don't want to) do anything about invoking plain subs as if they were methods. Offhand I don't see any reason why not to allow small trampolines to still be plain subs:

class C {
  method one { ... }
  method two { ... }
  sub three { rand > 0.5 ? shift->one : shift->two }
}

Imean sure we should encourage folks to write that instead as

  method three { rand > 0.5 ? $self->one : $self->two }

but I don't currently see any great harm in not permitting it anyway.