Front page | perl.perl5.porters |
Postings from March 2022
Op 11-03-2022 om 22:25 schreef Dan Book: > > Depends on how it is used in Perl syntax. If you write that as the > literal value: `my $x = 01730;` then you have not assigned the > zipcode, but an octal number. If you write it as a string: `my $x = > '01730';` then it will be a string containing your intended zip code. > Thus you must represent zipcodes as strings. Regardless, this is not > very relevant to the proposed functions; if anything, they allow a > serializer to avoid misrepresenting such a value, as long as you > created it properly. > > Not 'if anything', it's the whole point! Perl never had a problem, you create a string, treat it as a string, and it will be a string. However, a serialiser could make a mess, as it could not distinguish a number from a string, so it could conceivably interpret '01730' as a number. With the proposed changes the serialiser can see that it "is" a string, so it round trips back to a string, and not a number. M4Thread Previous | Thread Next