3 ms·
I think I will go about this slightly differently. When I finally get around to writing the language I have in my mind, it won't have a "new" stdlib, it'll prob
by lclarkmichalek 14y ago
I think I will go about this slightly differently. When I finally get around to writing the language I have in my mind, it won't have a "new" stdlib, it'll probably just use the python standard library (with modifications for changed semantics). I guess one could say that it could be a potential source of issues, as there will be some concepts that just do not map from one language to the other. However, seeing as I'll probably be the only one using it, I'm not too worried.
- tikhonj 14y agoThat's a completely reasonable approach (although I personally would choose something other than Python as my base). In fact, a bunch of languages do this already--most any JVM language (especially ones unique to the JVM) and .NET language take most of their standard libraries from Java or C#. The fundamental problem with this approach is that either your language is too different from the host for the library to map perfectly or it's too close to the host too be terribly interesting.
- riffraff 14y agothe problem with using an existing stdlib (semantic incompatibilities aside) is that then you end up unable to fix the warts. Say, you are annoyed by dicts' oddly named `has_key` and `fromkeys`, either you change them (yet another stdlib) or you don't (no improvement).