Perl is not a “strongly typed” language.
True for some definitions of “strongly typed“ (see Strong_typing), but in this context I think it’s clearer if we describe Perl as dynamically typed, in contrast to languages like C which are statically typed. With static typing, a variable’s type is known at compile time; with dynamic typing, a (scalar) variable’s data type is determined at runtime, and may change as the script executes — $foo may hold a string, then an integer, then a reference, ...
You cannot now say my $foo : integer;
Well, not in core Perl, no. But if you have objects, you’ll probably be using an object system (and if not, please see the picture on Your Mother’s home page!), and in an object system like Moose you can certainly specify that $foo is an Int. Here is one way to approach the OP’s task using Moose:
But this is still dynamic typing: if a type mismatch occurs, it is a runtime error which results.
Hope that helps,
| [reply] [d/l] [select] |
| |
> You cannot now say my $foo : integer;
O RLY?
see attributes for enabling
my $foo :integer;
and the parser also allows "typing"
DB<105> {package Int}
DB<106> my Int $x
=> undef
... though w/o much benefit.
Cheers Rolf
( addicted to the Perl Programming Language)
| [reply] [d/l] [select] |
I understand that, I was primarily using the int and boolean as an example, I understand they both would be considered scalars until I assign them some value. The main point I was trying to get across was how I could get both those data types into one unit, in this case an object. The usefulness of this, for my particular case, is quite useful for the application I have desired for it. It should make the data easier to manage. | [reply] |