Bob Blick wrote: > Wouter van Ooijen said: > >> How about Perl and Tk? Works for me. > > > > Yuk (Perl) and fantastic (Tk). I would suggest Python/Tkinter, or > > Tcl/Tk. Notice the common part in these three alternatives :) > > Huh? > > My post was in reply to someone suggesting BASIC, and you are dissing Perl > instead? As I don't remember seeing anyone else mention BASIC in this thread I can only assume you are refering to XCSB. Perhaps I should point out that XCSB actually runs native on a PIC. The compiler produces optimised machine code that executes directly on the PIC. I have not yet come across a compiler that generates native PIC machine code from Perl or Python source. > > I certainly hope it's only because you are taking time to carefully > compose a message detailing all the reasons why BASIC in any shape is bad > :-) Come on, get real. There are hundreds of dialects of BASIC some with very similar capabilties to C and C++, others with brain dead restrictions no better than assembler. The fact that you can get some crap code written in BASIC is not the fault of the language but the person writing the code. I have come across hundreds of examples of crap code written in C, C++, assembler, PASCAL, Fortran and SQL. But by far, the worst code I have ever had the misfortune to work on was written in C. The language isn't the problem - people are the problem. > > Really, so many good things can be done quickly and easily in Perl, and it > is way more popular than Python. No it isn't more popular, I dislike each equally ;-) > > Python might have had a chance to catch on if it hadn't been for the use > of indents rather than brackets. As it stands, it is doomed to always be a > niche language like FORTH. > I remember when C was seen as a terse super nerdy language only just better than APL and that period seemed to last for years :-) All the best. Regards Sergio Masci -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads