Unsigned variables

[wilbert]

Why put energy into a discussion like this about releasing source code.
Every one is free to do so or not.

It's better to explain what unsigned procedures are required and if both x86 and x64 are required or only one of them.
It's not that complicated to write them since asm has support for both signed and unsigned values.

[StarBootics]

It's not that complicated to write them since asm has support for both signed and unsigned values.

It's probably true if you know how to write ASM code ! Unfortunately for me, my knowledge of asm programming is between 0 and nothing.
In almost case, if I have a code example, I'm able to adapt it to fit my needs.

Do you see the problem ?

Regards
StarBootics

[ozzie]

+1 for unsigned longs, etc.

But in the interests of sharing code, I'll add a posting to "Tricks 'n' Tips" for my solution to a need that came up a few days ago. I needed to pass a key to an external procedure where the key is derived from an algorithm that uses lrotl (long rotate left) several times. So I wrote my own lrotl procedure in PB (not ASM). I had to specifically code for negatives as >> on an negative long propagates the sign bit.

[Little John]

Why not ?

Because it's part of my programming "toolkit", carefully crafted over the past 50 years to allow me to make a modest living using the talent that the Gods have bestowed upon me.

No comment.

[chris319]

We have 1- and 2-byte unsigned variables.

That leaves 4 bytes and 8 bytes. We're already half-way there.

For whatever reason, the PB team has decided to go only half way.