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

Home » Public Forums » archive » Re: Length of command line input
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Length of command line input [message #49546 is a reply to message #49545] Thu, 03 August 2006 12:39 Go to previous messageGo to previous message
news.qwest.net is currently offline  news.qwest.net
Messages: 137
Registered: September 2005
Senior Member
"TimLS" <tlsmith@qinetiq.com> wrote in message
news:1154624404.138340.291020@i42g2000cwa.googlegroups.com.. .
> I couldn't find the answer to this in the online documentation but
> perhaps someone has seen this before, or can suggest a good work
> around.
>
> I have a procedure which takes lots and lots of keywords, many of which
> are really long filenames, e.g.
> test_program,input1='really_long_filename1',input2='really_l ong_filename2',....


Change this to:
test_program,input1='really_short_filename1',input2='really_ short_filename2',....but seriously,1) make an array and pass the array as a keywordor2) write a function called "get_really_long_filenames" and callthat function from inside test_programor3) programatically create the filenames on the flyor4) get the filenames from a directory listing (assuming these files exist)or......or8671) increase the length of the text that the IDL command line willaccept.:)Cheers,bob
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: tile of IDLgrAxis
Next Topic: Interpolation question

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

Current Time: Sat Oct 11 08:26:12 PDT 2025

Total time taken to generate the page: 1.60179 seconds