comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » IDL verses other interpertative languages (tcl/tk, khouros, pv_wave, etc).
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
IDL verses other interpertative languages (tcl/tk, khouros, pv_wave, etc). [message #10551] Tue, 16 December 1997 00:00 Go to previous message
Stuart E. Murray is currently offline  Stuart E. Murray
Messages: 1
Registered: December 1997
Junior Member
I am working on a Satellite Sensor Simulator and will require that I
display several windows of data. I am trying to sort out what display
package might be the best bet. My group currently uses IDL and tcl/tk
and I have been asked to considered them since they are in house. I have
talked with these folks about both languages and both have strong view
points. It is obvious to me that this discussion group will also. But,
for the sake of argument. I will pose this question on the tcl
discussion group as well.

Has anyone done a pro or con evaluation about IDL (from RSI) verses
other languages like tcl/tk?

1. I will have a real-time connection to another embedded machine.
2. There will be one data spigot (be it parallel port, USB, serial port,
or network) to the other embedded machine. Does IDL support interfaces
such as those or do I have to write my own drivers?
3. Has anyone used IDL in a real-time environment successfully (or
unsuccessfully)?
3.1 The display of data in real-time may not be a strong issue if you
can throw a lot of horsepower at the problem. However, since IDL is an
interpertative language, you have to wonder about the impact of
performance over straight compiled code? Is this a problem? Is Windows a
problem?
4. How hard is it to incorporate C/C++ code into IDL? Literature
suggests a thorough knowledge of IDL before attemping this and I don't
have that yet.
5. IDL will probably be executed on a Laptop (166 MHz or better) under
Win95 or NT (the OS may have a Real-Time exec handler, although there
are people that would question a Real-Time exec handler can be done
correctly). Other real time OSs might be considered like VxWorks, QNX,
etc.
6. IDL learning curve steep?
7. What is the downside of IDL? (bloat code, etc).
8. IDL cost (both for the software & maintenance of code)? How easy is
it for someone to come in and pick up where you have left off?

I would appreciate your comments. If this is not the place for this
discussion, I apologize for the intrusion.

Stuart

------------------------------------------------------------ ----
Stuart Murray
Sandia National Labs.
Testers & Experimental Ground Stations Dept. 5715, M/S 0965
Bldg 890 Room 1048
Email: semurra@sandia.gov or snmurray@worldnet.att.net (home)
Phone: (505) 844-0160 (Office) or (505) 898-2795 (Home)
Fax:: (505) 844-5993 (Office) or Pager 845-0142-5066 (SNL/A)
------------------------------------------------------------ ----
[Message index]
 
Read Message
Read Message
Previous Topic: Mouse and keyboard events in a draw widget
Next Topic: "standard" ASCII file format

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu Oct 09 23:50:49 PDT 2025

Total time taken to generate the page: 1.08157 seconds