Jira (PUP-3170) Cap integer and float sizes

[Andy Parker (JIRA)]

Title: Message Title

Andy Parker commented on an issue   Re: Cap integer and float sizes What is the difference between this an PUP-3133? The way I read this is that this one is to cap the sizes in the implementation and the other one is to define it in the specification. If that is the case, then we can cap the size later to bring the implementation into conformance with the specification. Add Comment   Puppet / PUP-3170 Cap integer and float sizes The language specification says that Integer and Float becomes BigInteger and BigDecimal automatically. In reality this will not work since the rest of the infrastructure (notably binary serialization and Puppet DB) encodes integers as 64 bit signed, and floats as IEEE 754 binary64. We should change the specification to put this cap on the size. We ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.