Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Perl to Python 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ... the one point I would concede is that because Python is easy to embed, it may well be easier to integrate into some of those weird film animation programs.

    While I don't know specifics, if their choices came down the raw c, python and say javascript, I'd probably pick Python too.

    • Like they said, accessing their C++ libraries is a lot easier in Python. While I'm not familiar with doing that in Python, I'm sure it can't suck as much as in Perl. Or is there some other reason that there are oftentimes no Perl bindings (or ancient and badly supported) for a particular C/C++ library, whereas there are for Python. Is it just that Python is more popular, or that Python as a language matches up better with C++, and nothing to do with the suckiness of XS?

      I wonder myself why they don't use Lua [wikipedia.org]. I thought that was a popular scripting language especially in game-programming, so I'm not sure why it wouldn't be for computer graphics in general.

      • Lua is minimalist. Even though it looks like a wonderful technology for embedded scripting engines, it doesn't have a history of many mature and varied libraries to get you up quickly. It seems like the people at game programming get over it because they really just need the scripting engine and all else is hand-rolled with the game. I don't know if that's the same for film industry.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.