comp.lang.idl-pvwave archive: archive » Re: Getting running routine name

Home » Public Forums » archive » Re: Getting running routine name

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Getting running routine name [message #33543 is a reply to message #33542]

Thu, 09 January 2003 09:15

David Fanning
Messages: 11724
Registered: August 2001

Senior Member

Harro Uwe Hieninger (hiening@zi.biologie.uni-muenchen.de) writes:

> right you are !
>
> I left the solution to the reader, so that he could consult the online
> help and understand what he is doing
>
> ;-))

Oh, of course. I use that pedagogical trick myself from
time to time. :-)

> BTW, the strCompress call is not really necessary for THIS purpose, is it?

Probably not. I stole this from some working code. I'm
sure there is a reason for it somewhere. :-)

Cheers,

David

--
David W. Fanning, Ph.D.
Fanning Software Consulting, Inc.
Phone: 970-221-0438, E-mail: david@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155

Report message to a moderator

[Message index]

		Re: Getting running routine name By: sheryn.gillin on Thu, 09 January 2003 14:41
		Re: Getting running routine name By: Stein Vidar Hagfors H[2] on Thu, 09 January 2003 11:15
		Re: Getting running routine name By: David Fanning on Thu, 09 January 2003 09:46
		Re: Getting running routine name By: Pavel A. Romashkin on Thu, 09 January 2003 09:28
		Re: Getting running routine name By: David Fanning on Thu, 09 January 2003 09:15
		Re: Getting running routine name By: hieninger on Thu, 09 January 2003 08:51
		Re: Getting running routine name By: David Fanning on Thu, 09 January 2003 08:23
		Re: Getting running routine name By: hieninger on Thu, 09 January 2003 08:17

Previous Topic:	getting structure elements by tag name string
Next Topic:	map all-sky image

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu Oct 09 02:59:41 PDT 2025

Total time taken to generate the page: 2.23676 seconds