[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: idl2matlab translate-o-matic
- Subject: Re: idl2matlab translate-o-matic
- From: davidf(at)dfanning.com (David Fanning)
- Date: Tue, 22 Feb 2000 08:08:37 -0700
- Newsgroups: comp.lang.idl-pvwave,comp.soft-sys.matlab
- Organization: Fanning Software Consulting
- References: <Pine.LNX.email@example.com> <MPG.firstname.lastname@example.org> <email@example.com> <MPG.firstname.lastname@example.org> <email@example.com> <MPG.firstname.lastname@example.org> <email@example.com>
- Xref: news.doit.wisc.edu comp.lang.idl-pvwave:18543 comp.soft-sys.matlab:62846
David McClain (firstname.lastname@example.org) writes:
> Perhaps "better than MatLab", but hardly what "professional programmers"
Well, I admit I didn't conduct a scientific study, but
I was thinking about what my friends and I like. We're
pretty professional, at least most of the time. Say before
the beer arrives. :-)
> What can you say of a language that is purely array oriented, but
> cannot comprehend the existence of an empty array?
I don't know. I don't know what an empty array is either.
Perhaps that's why I like IDL.
> What of a language that
> can itself reclaim memory from unused arrays, but forces the user to reclaim
> "pointers" and "objects"? Etc., etc., ...
I'm sorry, but I think this *completely* misses the point.
Cleaning up variables is one thing, but checking for *every*
pointer reference at the end of every program module that
exits would bring just about any program--never mind IDL--
to a complete stand-still. It shouldn't be done. I applaud
the folks at RSI for dismissing the idea out of hand.
David Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438 E-Mail: email@example.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155