3 ms·
> With languages like Go you can easily end up with a panic if you’re not careful (where you’re trying to cast a nil interface{}) How is this any different to
by peteretep 7y ago
> With languages like Go you can easily end up with a panic if you’re not careful (where you’re trying to cast a nil interface{})
How is this any different to the runtime error you’d get in Perl if you attempted a method call on an undefined value you’d expected to be an object?
- pushpop 7y agoIt’s different because the DBI wouldn’t return an object for a nullable table record. Which is what we are specifically talking about. Sure other parts of your code might fail if you’re trying to use a scalar as an object (or such like) but that would consistently fail regardless of nullable types on the database. So I’m not going to argue that Perl doesn’t also have its own hidden traps (a great many of them in fact) nor that it’s interpretation of OOP isn’t terrible but the scope of this discussion was about nullable types and not anything else you now want to draw into the argument.