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

Home » Public Forums » archive » Re: Checking for perl
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: Checking for perl [message #52908 is a reply to message #52907] Wed, 07 March 2007 07:22 Go to previous messageGo to previous message
wlandsman@jhu.edu is currently offline  wlandsman@jhu.edu
Messages: 12
Registered: September 2006
Junior Member
"> >
> command="perl -e 's/%%Title: Graphics produced by IDL/%%Title:
> "+new_title+"/' -p " + filename + " > bp_pstitle.temp"
> command2="rm "+filename
> command3="mv bp_pstitle.temp " + filename
>
> spawn, command
> spawn, command2
> spawn, command3
>

As a side note, you could replace the second and third spawn commands with
the OS-independent FILE_DELETE and FILE_MOVE commands.

Maybe you can just run a simple test perl program and capture the output
from spawn.
For example,

spawn,'perl -h',tt
if N_elements(tt) GT 1 then begin
;Now do the real perl command
endif else message,'PERL not installed, postscript file not updated'

Another kludge would be write a little IDL program that reads the postscript
file one line at time, tests for the presence of the "IDL graphics" line
and updates it and writes the line to a new postscript file. Or you
could read the entire postscript file into an IDL string array, and then do
a global replace on the offending text.

--Wayne
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: hist_nd question
Next Topic: mapping volume data

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

Current Time: Fri Nov 28 14:06:57 PST 2025

Total time taken to generate the page: 0.63471 seconds