[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sas-l
Subject:    Re: HASHING getting different results for same string
From:       Michael Oujesky <reflectors () OUJESKY ! NET>
Date:       2023-04-23 22:16:06
Message-ID: 20230423221609.C611A1861CE () pb-smtp2 ! pobox ! com
[Download RAW message or body]

Interesting, but still looks like the HASHINH functions night have a bug,

Michael

At 01:47 PM 4/23/2023, Bartosz Jabłoński wrote:

>Take a look at the result of the LENGTHC() function.
>
>
>filename DESCRIPT TEMP;
>
>data _null_;
>file DESCRIPT;
>put "a";
>put "bb";
>put "ccc";
>put "dddd";
>run;
>
>options ls =max ps=max;
>
>DATA _NULL_;
>       INFILE DESCRIPT LENGTH=REC_LEN;
>       INPUT @;
>                    DESCRIPTORS = _INFILE_;
>          CRC32 = HASHING('CRC32',_INFILE_);
>          MD5   = HASHING('MD5',  _INFILE_);
>          STR_LEN = LENGTH(_INFILE_);
>          STR_LEN_M = LENGTHM(_INFILE_);
>          STR_LEN_C = LENGTHC(_INFILE_);
>          PUTLOG _N_= @10
>                 CRC32= MD5=  STR_LEN= STR_LEN_M= STR_LEN_C= REC_LEN=
>          ;
>          CRC32 = HASHING('CRC32',DESCRIPTORS);
>          MD5   = HASHING(  'MD5',DESCRIPTORS);
>          STR_LEN = LENGTH(DESCRIPTORS);
>          STR_LEN_M = LENGTHM(DESCRIPTORS);
>          STR_LEN_C = LENGTHC(DESCRIPTORS);
>          PUTLOG _N_= @10
>                 CRC32 MD5=  STR_LEN= STR_LEN_M= STR_LEN_C= REC_LEN=
>   ½        ;
>RUN;
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic