3 ms·

Your arguments seem to equally apply to using third-party libraries at all. Are you suggesting that it's better to (for example) re-implement HTTP rather than

Your arguments seem to equally apply to using third-party libraries at all. Are you suggesting that it's better to (for example) re-implement HTTP rather than use libcurl?

WalterBright 13y ago
I'm saying you've got to have pretty strong arguments to make a project dependent on a third party tool, if you expect to distribute it, expect it to be long lived, and expect to port it to many platforms.
- haberman 13y ago
  Yes I agree with the point that the portability of your dependencies limits your own portability. This is definitely something that is dependent on the tool or library though. For example, if you decided to use Lua as a tool, it is extremely unlikely that the portability of Lua will be a limiting factor. It is very likely to be more portable than your code (given that it compiles unmodified on Turbo C 1.0 from 1990: http://www.youtube.com/watch?v=-jvLY5pUwic http://www.youtube.com/watch?v=-jvLY5pUwic) So I definitely agree with "choose your dependencies wisely."
  - snogglethorpe 13y ago
    ...and if you decided to use Lua, you could also use LPEG, which is amazingly well suited to tasks like this... [LPEG is also a dependency of course, but pretty small (just include its source code along with your own) and super portable in the same way Lua is.]
- deleted 13y ago
  [deleted]