use Perl

s/Auto/Anon/ # cut and paste fail

The code sample you posted is almost there. You just need to create an anonymous package name instead of using __PACKAGE__. I would simply append the accessor names to the base class, e.g. Object::Anonymous_ding_wong_line

    sub new {
        my $class = shift;
        my %args = @_;
        my $self = { };
        my $name = join('_', $class, keys %args);

        for my $arg (keys %args) {
            # Store the given value
            $self->{$arg} = $args{$arg};

            # Create the accessor
            my $methname = $name . "::" . $arg;
            *{$methname} = sub {
                my ($innerself) = @_;
                return $innerself->{$arg};
            };
        }

        bless $self, $name;
    }

You can use Class::MOP::Class as chromatic notes. Or here's a similar thing using Badger::Class:

    package Class::Auto;

    use Badger;
    use Badger::Class 'class';

    sub new {
        my ($class, %self) = @_;
        my $name = join('_', $class, sort keys %self);
        class($name)->accessors(keys %self);
        bless \%self, $name;
    }

And here's an example of use:

    use Class::Anon;

    my $object = Class::Anon->new(
        x => 10,
        y => 20,
        z => 30
    );

    print ref $object, "\n"; # Class::Anon_x_y_z
    print $object->x, "\n"; # 10
    print $object->y, "\n"; # 20
    print $object->z, "\n"; # 30


I have to say, I find the whole idea of POD interspersed with code quite loathsome. It appreciate all the reasons why it's a Good Thing (which boils down to keeping the docs as close to the code as possible), but it has so many drawbacks.

Most notably, it makes it hard to skim through the code when there's big globs of POD getting in the way. If I'm reading the source then it's code I want to concentrate on. If it's the end-user documentation that I want then I'll use perldoc or look at an HTML version of the docs.

It reminds me of the Bad Old Days when CGI scripts were written as an impenetrable mix of Perl code and HTML markup. We learned our lesson on this a long time ago - a separation of concerns is a good thing.

Another problem is that it forces you to write your POD to match the structure of your code or vice versa. This is wrong. The end-user documentation should be written from the perspective of someone wanting to use the module. This is an entirely separate thing from the way that the module is implemented internally. After all, that's what programming is about - creating "black box" abstractions that hide the details of the internal workings.

IMHO, code should be interspersed with comments to explain how the code works, and the end-user POD documentation should be placed at the end of the file. That way you don't have any of the problems with Perl code getting mixed up with POD. Things are badly wrong when you have to change your coding/indenting styling to fit in with the embedded documentation.

But that's just my HO, of course. Each to his/her own.

OK, I'll put the first stick in the ground.

I've put a few ideas together for a *.perl.org facelift. I chose use.perl.org as a starting because that was the original subject of discussion.

http://wardley.org/use.perl.org/test.html