newRPL - Updated to build 1510 [official build remains at 1487]
|
09-08-2021, 10:40 PM
Post: #186
|
|||
|
|||
RE: newRPL - Updated to build 1497 [official build remains at 1487]
(09-08-2021 09:28 PM)Claudio L. Wrote: As far as TAGs, all tagged objects TYPE is 10000 + the type of the tagged object, so you don't really need to strip the tag to type check it. Huh, didn't realize it! Quote:Perhaps we could use exact/approximated numbers in the list to indicate a "loose" comparison. But this would mean to devise a comparison schema that is radically different from the one used by TYPEE. We would end having two incomplete features instead of one. Inspired by the initial implementation of TYPEE I drafted a proposal that can be adapted to all object types and it's based on the principle that each property is encoded by a decimal digit different from zero. The zero being a wildcard when the extended type is interpreted in the context of type matching. For example, the extended type for real numbers would be like this: Therefore the extended type of 123.45. becomes 10.12122 and you can extract (with DIGITS perhaps?) all the info you might need. In type-checking this value would still match against 10(.00000) if you need a simple real or against 10.1002 if you need a finite approx. Real numbers are the building block of more complicate types therefore if you need to check for a temperature increment greater or equal to zero (or a variable containing it) you would do Code:
Since unit subtype describes only properties relevant to unit objects and not relevant to the "payload". |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 2 Guest(s)