News for hackers. Stuff that matters.
Re:Why we used Pony to write Wallaroo by model_m_warrior on Thursday October 26, 2017 @01:21PM (#15561003)
Are Ponys classes akin to Erlang modules or does it take a more enterprise-y perspective on OOP?
Re:Why we used Pony to write Wallaroo by scottlf on Thursday October 26, 2017 @03:27PM (#15562185)
Howdy. Erlang's modules are involved in code namespace for the compiler & runtime (i.e., the 'M' of the 'MFA' triple of Module + Function name + Arity that names a function) as well being the unit/scope/bound for hot code loading (i.e., you must load or unload an entire module at a time).

I've worked in Erlang-land far longer than I've lived in any OOP-land, so I'm not sure what you mean by enterprise'y OOP. Coincidentally, Pony's rules for "Packages" are something I just smacked my ignorant head against a few hours ago. The subsections of https://tutorial.ponylang.org/packages/ in the tutorial can probably answer at least some of your question: specifically "Package System" and "Use Statement".

Re:Why we used Pony to write Wallaroo by pdimitar on Thursday October 26, 2017 @04:30PM (#15562741)
I'll take the liberty to speculate and assume your parent comment was asking if Pony classes have the same features as Java classes -- namely class-level attributes, instance-level attributes, different access levels to attributes and methods. Those things.

So, does it?

Re:Why we used Pony to write Wallaroo by spooneybarger on Thursday October 26, 2017 @04:42PM (#15562814)
Pony classes have methods. Pony classes have fields.

Fields and methods can be public or private. Private is akin to Java's package private.

There are no instance variables.

Re:Why we used Pony to write Wallaroo by pdimitar on Thursday October 26, 2017 @08:54PM (#15564678)
Thank you. And structs / records? I mean, if there are no instance fields, there has to be some kind of constructs that emulate them.
Re:Why we used Pony to write Wallaroo by spooneybarger on Thursday October 26, 2017 @09:26PM (#15564854)
Sorry, I mispoke. There are no class fields. Only instance fields.
Re:Why we used Pony to write Wallaroo by aturley on Thursday October 26, 2017 @01:45PM (#15561244)
I'm not sure which features of Erlang modules you're interested in comparing to Pony classes, but I'll take a stab at trying to answer.

Pony classes are defined using a "class" keyword. Classes have properties and functions, where functions are like methods that you would find in a language like Java. Pony supports structural subtyping via interfaces and nominal subtyping via traits, and it disallows multiple inheritance.

I'm not sure how much that helps, but if you have more specific questions I'd be happy to try to answer them. I'm a little rusty on my Erlang, but hopefully it will come back to me.