[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SPAWN + readU + strings
- Subject: Re: SPAWN + readU + strings
- From: Craig Markwardt <craigmnet(at)cow.physics.wisc.edu>
- Date: 17 Apr 2000 19:13:16 -0500
- Newsgroups: comp.lang.idl-pvwave
- Organization: U. Wisc. Madison Physics -- Compact Objects
- References: <38FB2013.5AC0F96E@lmco.com> <MPG.1364de5e7f08deb4989ada@news.frii.com> <38FB5E04.353A1C1B@lmco.com> <MPG.13652c08737408e2989adb@news.frii.com> <38FB82E7.927BACA0@lmco.com> <MPG.1365381467bbd69d989add@news.frii.com>
- Reply-To: craigmnet(at)cow.physics.wisc.edu
- Xref: news.doit.wisc.edu comp.lang.idl-pvwave:19330
davidf@dfanning.com (David Fanning) writes:
> Ramji Digumarthi (ramji.digumarthi@lmco.com) writes:
>
> > WEll!! I tried that. Either temperary variable (actually recasting the
> > variable as long) or legitimate variable work as long as I do not read
> > the string variable. Once I read the string variable, the next readU of
> > a variable goes hay wire...
> > So what gives????
>
> I don't know. But I'm really not the person you should be talking
> to. And I wouldn't be trying to write strings anyway. I would
> be writing and reading byte values and casting them back
> to strings. Can't much go wrong that way. :-)
Amen to that. Read bytes, and then convert to a string at the end.
But your specific problem reminds me of a story: A man goes to the
doctor and says, "Doctor, it hurts when I do this." The wise doctor
said, "Then don't do that."
Seriously, if by *not* reading the string variable, everything works
fine, are you sure that the string is there?
Craig
--
--------------------------------------------------------------------------
Craig B. Markwardt, Ph.D. EMAIL: craigmnet@cow.physics.wisc.edu
Astrophysics, IDL, Finance, Derivatives | Remove "net" for better response
--------------------------------------------------------------------------