Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: 3e18f726ee600af6c417719a516fdb303ee2e9a4
https://github.com/Perl/perl5/commit/3e18f726ee600af6c417719a516fdb303ee2e9a4
Author: Lukas Mai <[email protected]>
Date: 2025-03-11 (Tue, 11 Mar 2025)
Changed paths:
M pod/perldata.pod
Log Message:
-----------
perldata: document binary/octal floating-point constants
This (possibly accidental) feature has had tests since commit
58be57636a and bug fixes such as commit 2cb5a7e8af. See also the
discussion in GH issues #16114 and #14791, particularly jhi's comment in
<https://github.com/Perl/perl5/issues/16114#issuecomment-544090886>:
> Relatedly: I remember there being a known "loophole" so that the
> scanning code currently accidentally, falling naturally out of the
> implementation, is also doing "binary fp" and "octal fp". Ah yes:
>
> ./miniperl -wle 'print 0b11.1p0'
> 3.5
> ./miniperl -wle 'print 011.1p0'
> 9.125
>
> This is probably not documented anywhere. I can't now think of the
> right search terms to find any previous discussion, there was something
> about should this be rejected, or not. If not (as is currently the
> case), maybe this possibly should be tested, documented, and made
> official?
With the documentation in this patch and the existing tests, I guess the
feature is now official.
Fixes #18664.
Commit: 4b98c87fc7ce5f3faf31d98a80ec92289b501580
https://github.com/Perl/perl5/commit/4b98c87fc7ce5f3faf31d98a80ec92289b501580
Author: Lukas Mai <[email protected]>
Date: 2025-03-11 (Tue, 11 Mar 2025)
Changed paths:
M pod/perldelta.pod
Log Message:
-----------
perldelta: binary/octal floating-point documentation
Compare: https://github.com/Perl/perl5/compare/fe38c5ac7b54...4b98c87fc7ce
To unsubscribe from these emails, change your notification settings at
https://github.com/Perl/perl5/settings/notifications
