moose | Multiphysics Object Oriented Simulation Environment

You may use this awk:

I used to work with Moo but it seems to be the same. You just need to declare the property in the subclass using + to override previous declaration.

Moose is for building classes and roles. While you technically can also export functions, it's not necessarily the best idea.

Here's an example Moose class which also exports a function.

MyApp/Widget.pm

You can use data attributes

tag is not a recommended/known tag attribute

Also slow down on the template literals. I choose to use input event listener too since it handles paste

Sort values by type and population:

• type by ascending order because 'C' is before 'P'
• population by descending order to have highest values at top

Then group by id and state columns and finally take the first value of each group:

I have, with the very kind and patient assistance of @simbabque, managed to work this out.

simbabque suggested I set the lang attribute to lazy, which did work:

[Note: I'm am a former maintainer of Exporter]

I believe you've confused exporting with inheritance. That's easy to do, Perl doesn't draw a line between "function" and "method", they're just sub.

tl;dr You don't need to export, that's just how inheritance works, there is a work around.

Exporting lets you call a function from outside of a package without fully qualifying it. It would let you call Foo::hello as just hello. Exporting lets Perl know that hello really means hello in package Foo.

But these are method calls, and you call them on a class or object. my $foo = Foo->new; $foo->hello. No exporting required. Foo->new calls new in Foo and returns a Foo object. $foo->hello knows to look for the method foo in the ancestry of $foo's class. You don't need to use exporter in a class, that's what "Do not export method names" means.

Exporting is a deliberate act which copies symbols around. Inheritance is all or nothing. If you inherit from a class you get all its methods (subs). This is a consequence of inheritance, and there are many other alternatives to inheritance such as composition.

In other OO languages you could declare the method private and it would not be inherited. Perl doesn't have that. Normally you just live with this by convention as you have, put an underscore in front of the method name, don't document it, and if somebody uses it that's their problem. And that's usually fine.

But you can make truly private methods with anonymous subs and lexical variables.

Mask the values in place column which are not equal to 1 then group the masked column by subject and class and use ffill to forward fill the values

I used answers from here and here to make compose this. Here is one way you might do it, using the string class to get rid of punctuation and numbers.