Re: Probably for David Cuny

new topic     » goto parent     » topic index » view thread      » older message » newer message

Terry Moriarty writes:
> I'm then converting the resulting 3 integers to an ASCII string with
> spaces. The conversion works correctly...

> my_string(on trace window)
>   = {32,50,54,48,48,32,49,53,50,50,32,53,52,51,57,56,55,50}
>   which translates to " 2600 1522 5439872"
> but the window title displays 2600 1511 5428861

> One thing I have noticed; when the string is shown in the
> trace window, after it has been *evaluated*, only the values
> of 32(space) and 48(0) have their ASCII equivalent displayed
> beside them. If I *directly* enter exactly the same string i.e.
>
>     my_string = {32,51,53,49...
> It shows *all* the ASCII equivs. Is this starnge or is it
> something to do with the trace procedure?

I suspect that your conversion is producing results
which are *very* slightly off in some cases. When you
display the results in the trace window they are
rounded (to 10 significant digits), so they look ok,
but in reality they are not exact integers.
Later they get rounded *down*. That's why you get
digits that are 1 less than they should be in some cases.
If you show us the code that you are using for the
conversion maybe we can spot where the (slight) error
is creeping in.

Regards,
     Rob Craig
     Rapid Deployment Software
     http://members.aol.com/FilesEu/

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu