Re: Accessing a scalar value in another subroutine?

Why do you want to do this rather than just use POD? ("I heart Python" is not a good reason.)

That having been said, there's actually a really easy way to do this for object-oriented code (i.e. subs designed to be called as methods rather than functions).

use v5.14;

package Foobar {
  sub new {
    bless [] => shift;
  }
  sub quux {
    return "documentation" unless @_;
    say "The method has been called!";
  }
}

my $obj = Foobar->new;
$obj->quux;            # calls the method
print Foobar::quux();  # prints the documentation
[download]

perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'

Comment on Re: Accessing a scalar value in another subroutine? Download Code

Replies are listed 'Best First'.
Re^2: Accessing a scalar value in another subroutine? by LanX (Saint) on Sep 23, 2012 at 21:01 UTC
> Why do you want to do this rather than just use POD? POD is normally used to describe the public API of a module and many people oppose weaving POD snippets close to subs. Furthermore automatically finding the corresponding POD-part for a function isn't trivial. Docstrings OTOH are closely tied and great for introspection in an interactive system, like REPLs or applications with embedded scripting. I'm inspecting LISP docstrings in emacs every day when browsing thru functions. Cheers Rolf	[reply]
Re^3: Accessing a scalar value in another subroutine? by Corion (Patriarch) on Sep 23, 2012 at 21:44 UTC
If you are hell-bent on doing that, and having doc-strings for your functions, the following style may be to your taste: `use vars %documentation; sub doc($$) { my ($for,$doc) = @_; $documentation{ $for } = $doc; }; doc('mysub1',<<'=cut'); =head2 C<< mysub1 >> This documents mysub1. An example: mysub1(); =cut sub mysub1 { ... }; doc('frobnicate',<<'=cut'); =head2 C<< frobnicate >> This documents frobnicate. An example: frobnicate(); =cut sub frobnicate { ... };` [download] You will note from history that this style never caught on. If you adhere to a strict documentation style, you may simply parse the POD and extract the function definitions from that. Using "docstrings" and parsing the module documentation are equivalent in that sense.	[reply] [d/l]
Re^4: Accessing a scalar value in another subroutine? by LanX (Saint) on Sep 23, 2012 at 21:51 UTC
well far from being DRY... :) Cheers Rolf	[reply]
Re^3: Accessing a scalar value in another subroutine? by Anonymous Monk on Sep 23, 2012 at 22:34 UTC
Furthermore automatically finding the corresponding POD-part for a function isn't trivial. Yes, it is absolutely trivial, provided the pod actually documents the function. Pod::Select/Pod::Coverage ...	[reply]