How does MonkeyC interpret numbers with more decimal places than Double can handle

Let’s say a web api returns a decimal number with more digits than Double can handle, for example 3.1415926535897932384626433832795028841971693. With MonkeyC being Duck typed what does it consider it an instanceof ?   

  • Then there's the pattern of defending Garmin against any and all criticism, minimizing bugs, and often assuming that when a bug is reported (either in CIQ or in a device), the problem is actually that the reporter is "holding it wrong" (lack of respect for the person reporting the bug, with the assumption that they have no idea what they're talking about.)

    This is really off topic but anyway....

    What seems more common to me (I'm exaggerating a little) is people saying things like:

    • It's stupid that Garmin devices are not like Android/iPhones.
    • Garmin (a long-established experienced company) is (implied) stupid for not doing what I think is a good idea (that Garmin likely already considered and dropped as unworkable).
    • How dare you suggest a practical work-around when you should be joining with me in complaining about something Garmin won't ever change.
  • They could be biting the hand that feeds them.

    In this case feeds a duff answer, because they didn’t take the time to read my question. It seems the correct answer, if you can change the web api, is to return it as a String then use toDouble() which I’ve got from yourself and Flocsy. Thanks.

  • they didn’t take the time to read my question

    No one is actually required to take this time.

    People sometimes miss things (which is what I suspect happened here).

    Jim's responses are generally more useful. He puts a fair amount of time into trying to help people.

    is to return it as a String then use toDouble() which I’ve got from yourself and Flocsy.

    (This was jim's suggestion.)

  • No one is actually required to take this time.


    If someone can’t be bothered reading a question, they could at least admit their mistake, when questioned on their incorrect answer.   

  • If someone can’t be bothered reading a question, they could at least admit their mistake, when questioned on their incorrect answer.  

    Unfortunately, you get what you get (not necessarily what you want). Jim is (generally) one of the more useful people in this subforum. For your own selfish reasons, you still might want him be a resource.

  • I was pointing out what Monkey C allows.  Only floats and doubles.  No more precision than a double. (so the "f" or "d" post)  

    I guess you didn't understand why I was saying that.  Sorry.