RE: [U2] Re: [UD] problem with hex conversions

2004-11-24 Thread Stevenson, Charles 
Bill,

You're forgiven  - but just cuz it's Thanksgiving tomorrow.

Chuck Stevenson, old primate


-Original Message-
From: Bill H.

Goes to show ya...coming from a Pick background I see nothing wrong with
the results.  :-)
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

RE: [U2] Re: [UD] problem with hex conversions

2004-11-24 Thread Bill H. 
Goes to show ya...coming from a Pick background I see nothing wrong with the
results.  :-)

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Simon Lewington
> Sent: Wednesday, November 24, 2004 3:35 AM
> To: [EMAIL PROTECTED]
> Subject: [U2] Re: [UD] problem with hex conversions
>
>
> Switch to $BASICTYPE 'U' to stop this supposed Pick-Style behaviour.
>
> Simon
>
> "Ben Gladman" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> >
> > I'm getting unexpected results from the hex conversions in
> Unidata 6.0.12
> on
> > NT:
> >
> > PROGRAM BJGTEST
> > *
> > CRT "OCONV('1','MO')=" : OCONV('1','MO')
> > CRT "OCONV('1','MO0C')=" : OCONV('1','MO0C')
> > CRT "OCONV('1','MX0C')=" : OCONV('1','MX0C')
> > CRT "OCONV('1','MX')=" : OCONV('1','MX')
> > CRT "ICONV('F','MX')=" : ICONV('F','MX')
> > *
> > STOP
> >
> >
> > the results I get are:
> >
> > OCONV('1','MO')=001
> > OCONV('1','MO0C')=061
> > OCONV('1','MX0C')=31
> > OCONV('1','MX')=31
> > ICONV('F','MX')=
> >
> > The octal conversions and the hex-ascii conversion seem okay.
> But I would
> > expect the fourth line to read '1' or '01', and the fifth line to read
> '15'?
> > Is this a problem anyone else gets?
> >
> > Cheers,
> > -Ben
> ---
> u2-users mailing list
> [EMAIL PROTECTED]
> To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

[U2] Re: [UD] problem with hex conversions

2004-11-24 Thread Ben Gladman 
Also just found out [[thanks Adam]] that if you put any other character at
the end of the conversion code, it works ok:


PROGRAM BJGTEST
*
CRT "OCONV('1','MX*')=" : OCONV('1','MX*')
CRT "ICONV('F','MX*')=" : ICONV('F','MX*')
*
STOP


produces:

OCONV('1','MX*')=01
ICONV('F','MX*')=15





"Simon Lewington" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]


Switch to $BASICTYPE 'U' to stop this supposed Pick-Style behaviour.

Simon
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

[U2] Re: [UD] problem with hex conversions

2004-11-24 Thread Simon Lewington 
Switch to $BASICTYPE 'U' to stop this supposed Pick-Style behaviour.

Simon

"Ben Gladman" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> I'm getting unexpected results from the hex conversions in Unidata 6.0.12
on
> NT:
>
> PROGRAM BJGTEST
> *
> CRT "OCONV('1','MO')=" : OCONV('1','MO')
> CRT "OCONV('1','MO0C')=" : OCONV('1','MO0C')
> CRT "OCONV('1','MX0C')=" : OCONV('1','MX0C')
> CRT "OCONV('1','MX')=" : OCONV('1','MX')
> CRT "ICONV('F','MX')=" : ICONV('F','MX')
> *
> STOP
>
>
> the results I get are:
>
> OCONV('1','MO')=001
> OCONV('1','MO0C')=061
> OCONV('1','MX0C')=31
> OCONV('1','MX')=31
> ICONV('F','MX')=
>
> The octal conversions and the hex-ascii conversion seem okay. But I would
> expect the fourth line to read '1' or '01', and the fifth line to read
'15'?
> Is this a problem anyone else gets?
>
> Cheers,
> -Ben
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/