2 ms·
who had no clear picture of making a consistent interface, even if only by convention. There are few conventions that are consistent across domains. As a concr
by dagw 5y ago
who had no clear picture of making a consistent interface, even if only by convention.
There are few conventions that are consistent across domains. As a concrete example I worked on a code base where functions from some libraries wanted angles as radians and the others wanted them as degrees. Both where internally consistent and followed all the relevant conventions for their domain, however when they intersected it was a pain.
- lolive 5y agoJust to open up the discussion, I am looking at the FMI [1] standard as a way to describe the interface of different block codes. And then try to generate the FMI description from static analysis of the Python function definitions. That’s my current plan of study. But as I said earlier, I have some background in static typing in Java, and I might find the current state of the art in Python not to be adapted to my idea. [1]: https://en.m.wikipedia.org/wiki/Functional_Mock-up_Interface https://en.m.wikipedia.org/wiki/Functional_Mock-up_Interface
- macintux 5y agoSomething that seemed common in Erlang, but less so in Python, was to annotate numbers using tuples. If you used both radians and degrees in a single code base, they’d be passed around as named tuples.