3 ms·

It was only technically python-like, but enough like it that you could conceivably call them the same thing.

• deleted 3y ago
  [deleted]
• joak 3y ago
  If it accepts a subset of python it's technically python: any codon-python program is a python program. Not full python but python nonetheless... My understanding: The goal is not to compile existing python code but to write new python code meant to be compiled in order to be faster. Limited use, still useful.
  • debatem1 3y ago
    It is trivially easy to write a codon program which runs in both Codon and Python but behaves differently in a way that is not considered a bug in either language. That means it is not a subset, unless by that you mean that each language has a subset of the other's programs which it can run. In which case C and JavaScript are the same language too.
    • netr0ute 3y ago
      Is there an example of this? I know there's several areas where Cpython has some funky undefined behavior, but those aren't particularly notable because they're by definition implemention dependent.
      • selcuka 3y ago
        Isn't fixed width integers as compared to arbitrary width an example of this?
      • cozzyd 3y ago
        print(repr(2**64))
      • debatem1 3y ago
        The 2**64 example given here is exactly right. You don't need undefined behavior or language lawyering to hit the difference; you just need a 65 element bitset.
• debatem1 3y ago
  Codon can't even run the whole python standard library. It changes integer semantic from arbitrary width to fixed width. Exaloop's own docs refer to the process of converting code between the two as "porting". Seems like if it isn't pythonic enough to run python code correctly it probably shouldn't be called "python".