User loginNavigation |
Good Language Design Principals for Scripting LanguagesI work for a vendor of an application for the management of trades. We would like to extend an application with a simple scripting language for batch processing. The idea being that someone non-technical could use a script to schedule processor intensive tasks, such as pricing a portfolio, to run over night. What we have in mind is something very simple just a few verbs and noun pairs, i.e. import "fixing.dat" The script would then be run by a scheduler. However, I vaguely remember a discussion on ltu about "ant" starting off like this with relatively simple objectives, but getting a bit bogged down because people inevitably used it for more complex scripting tasks. I think the designers of the language ended up saying they’d have been better off applying good language design principals up front. So my question is what sort of good language design principals should be applying to a litte scripting language like this? Or would it better to use an existing scripting language? Part of the application is written in caml so this would probably the scripting language of choice, but I’m a bit worried would be over kill. By Robert Pickering at 2007-07-02 08:08 | LtU Forum | previous forum topic | next forum topic | other blogs | 12622 reads
|
Browse archives
Active forum topics |
Recent comments
5 days 12 min ago
40 weeks 6 days ago
40 weeks 6 days ago
40 weeks 6 days ago
1 year 11 weeks ago
1 year 15 weeks ago
1 year 16 weeks ago
1 year 16 weeks ago
1 year 19 weeks ago
1 year 24 weeks ago