Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #50290
| From | Dave Angel <davea@davea.name> |
|---|---|
| Subject | Re: Best Scripting Language for Embedded Work? |
| Date | 2013-07-09 21:44 -0400 |
| References | <h7ept85p7jtc5e7j2ubl66k604d7cln3hs@4ax.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.4481.1373420706.3114.python-list@python.org> (permalink) |
On 07/09/2013 09:29 PM, David T. Ashley wrote: > We develop embedded software for 32-bit micros using Windows as the > development platform. > > We are seeking a general purpose scripting language to automate > certain tasks, like cleaning out certain directories of certain types > of files in preparation for ZIP'ing, generating certain source files > automatically, etc. > > Selection criteria: > > a)Should be able to compile the script interpreter as a monolithic > executable (no .DLL dependencies, etc.) for easy versioning and > distribution of the script interpreter. Oh, I thought you were going to run this on Windows. You're just developing it on Windows, and you want to cross-compile to target some other platform? Which? > (Note that I'm not asking > that the script be a single executable, just the interpreter. To run > a script you'd need both the script and the interpreter. The script > would be a text file, and the interpreter would be a single .EXE.) If you're also constraining your "program" to a single text file, you don't want Python. It uses modules, imported from your script to do much of the work. > > b)Should be extensible, in that one could add commands or library > functions to the script interpreter in C (for efficiency), and the > whole script interpreter could again consist of a single executable > with no other dependencies. (Note that I'm not asking that the script > be a single executable, just the interpreter. To run a script you'd > need both the script and the interpreter. The script would be a text > file, and the interpreter would be a single .EXE.) And that's supposed to HELP efficiency?? > > c)Should be able to spawn compilers and capture the output, do file > I/O, and all the other minor expected stuff. > > d)Graphical capability would be nice. > > I know that Tcl/Tk would do all of the above, I doubt it. > but what about Python? > Any other alternatives? -- DaveA
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Best Scripting Language for Embedded Work? David T. Ashley <dashley@gmail.com> - 2013-07-09 21:29 -0400
Re: Best Scripting Language for Embedded Work? Dave Angel <davea@davea.name> - 2013-07-09 21:44 -0400
Re: Best Scripting Language for Embedded Work? David T. Ashley <dashley@gmail.com> - 2013-07-11 21:14 -0400
Re: Best Scripting Language for Embedded Work? Alain Ketterlin <alain@dpt-info.u-strasbg.fr> - 2013-07-10 08:41 +0200
Re: Best Scripting Language for Embedded Work? Christian Gollwitzer <auriocus@gmx.de> - 2013-07-10 09:03 +0200
Re: Best Scripting Language for Embedded Work? Stefan Behnel <stefan_ml@behnel.de> - 2013-07-10 09:15 +0200
Re: Best Scripting Language for Embedded Work? Christian Gollwitzer <auriocus@gmx.de> - 2013-07-12 08:52 +0200
Re: Best Scripting Language for Embedded Work? Grant Edwards <invalid@invalid.invalid> - 2013-07-10 14:15 +0000
Re: Best Scripting Language for Embedded Work? Johann Hibschman <jhibschman@gmail.com> - 2013-07-10 14:38 -0500
Re: Best Scripting Language for Embedded Work? David T. Ashley <dashley@gmail.com> - 2013-07-11 21:19 -0400
Re: Best Scripting Language for Embedded Work? Stefan Behnel <stefan_ml@behnel.de> - 2013-07-12 06:17 +0200
csiph-web