|
Jeff Wise wrote:
Looks quite similar to the code I posted 2 hours ago :), perhaps a bit neater. It'd be b3*256+b2 though I believe. You are correct. Not one of my better moments. Unfortunately, these bad moments are becoming more frequent! I apologize.
Haha not a problem, I was actually wondering if the list had failed :). No one noticed!
wasn't it big endian? i didn't check, obviously.
I was just going off this statement: "For example, many length fields are X'2008' meaning 8200 bytes."Was reassuring to see both approaches were the same, and I learnt that string.byte takes a range (had forgotten that detail). :)
- Alex