Re: SSL Socket Client

[thomas@xxxxxxxxxxx]

I suspect the only reason it's confusing is because it's viewed on a single 
platform. The appropriate #define on some different platform probably has a 
different shift value. By using the macro, the resulting code becomes more 
portable.

However, since the the point of the thread is conversion of the C includes into 
ILE RPG, the whole question of portability becomes almost moot. I'd probably go 
with the constant '1' for the copy module and forget it afterwards. The only 
reason to keep the macro at all is keep a very slim hope alive that the 
resulting ILE RPG source code will be ported somewhere else someday. No?

Tom Liotta

On Wed, 20 February 2002, Jim Langston wrote:

> I agree, this one is totally confusing.  (1 << 0) means take the byte on the
> left, and shift it's bits to the left 0 times, resulting in 1.  I would
> expect
>
> #define SSL_ENCRYPT_MASK 1
> or
> #define SSL_ENCRYPT_MASK 0x01
>
> to do the exact same thing.  (0x01 meaning hex value, a little more self
> documenting saying this is a bit mask).
>
> The only thing I can think of, maybe at one time it was something like
> (1<<4) or something, and kept changing 'til it became (1<<0) and was left
> that way.

--
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788
Fax  253-872-7904
http://www.400Security.com


___________________________________________________
The ALL NEW CS2000 from CompuServe
 Better!  Faster! More Powerful!
 250 FREE hours! Sign-on Now!
 http://www.compuserve.com/trycsrv/cs2000/webmail/