[Isocops] Build problem

[DeMajistre, Bob]

Since this is going out over the list, I'll wait until tomorrow around noon
and assume I'm the one to fix this.

My conventions are slightly different, but I generally use SPAWN the same
way - i.e. temporary text file with input shoved into the spawned routine.


Bob


On 6/2/10 5:18 PM, "Geoff Crew" <gbc at space.mit.edu> wrote:

> You're the IDL expert, so I'll bet Ken will defer to you.  ;-)
> 
> I created the mess as I didn't know a quick way of passing the
> information between IDL and ibex_rotate.  I suspect IDL has some
> way of qualifying my (static) temporary name with one that is
> user and process specific--that certainly reduces the cross-section
> for this problem.
> 
> If I had been writing in shell syntax I'd have done:
> 
>   /tmp/IDLsuxReallyBadly-$USER-$$
> 
> (and of course, removed it 5 lines later) so there's little risk of
> filling up /tmp with such things, even if someone is agressively
> typing ^C.
> 
> In the normal operation the file should only exist for a fraction of a
> second (i.e. while ibex_rotate is running) and then be deleted by IDL
> which is why this is a "bump-in-the-night" sort of bug rarely seen.