3 ms·
I would argue if you "have to parse a very deeply nested" data format you should have subroutines or objects with methods for that specific task, and not rely o
by kqr 3y ago
I would argue if you "have to parse a very deeply nested" data format you should have subroutines or objects with methods for that specific task, and not rely on generic language container types.
What you're running into is insufficient modeling of the problem, not a deficiency unique to any language.
- tyingq 3y agoBut a Perl object underneath is a hash, or list, or whatever. That abstraction doesn't save you from Perl's "sigil per type" and other oddities. It maybe encapsulates it, but...