Re^2: Problems Getting the Template Correct when Using unpack()

I still have to work my way through these notes... Fanx!

...but to clarify what I was talking about re:

$data: !CI=427 Lamp dim state=2 SCATS=0.!

What I wrote was a mistake...

What I meant to say was: I show a "C" character (ASCII decimal 67, 0x43) at the start of the '$data' list of characters, when in the @data array you'll see it's actually a "special" character (ASCII decimal 128, 0x80).

I simply wasn't sure if the "special" character would upset some display thing if I included that unusual character in my posting... tha's all.

"Sorry about that, Chief...

Comment on Re^2: Problems Getting the Template Correct when Using unpack()

Replies are listed 'Best First'.
Re^3: Problems Getting the Template Correct when Using unpack() by AnomalousMonk (Archbishop) on Oct 10, 2017 at 10:53 UTC
... I show a "C" character ... it's actually a "special" character (... 0x80). Is this character always a 0x80 character? If it's always the same, do you really care about extracting this character (which looks like some kind of delimiter/placeholder)? If it varies, how does it vary? I was thinking about a regex-based solution, and a constant 0x80 in the middle of the record could be a nice little anchor. Update: Added `<blockquote>` block to start of node. Give a man a fish: `<%-{-{-{-<`	[reply] [d/l] [select]
Re^4: Problems Getting the Template Correct when Using unpack() by ozboomer (Friar) on Oct 10, 2017 at 21:09 UTC
No, it's something that can be a part of a message string OR it can be a flags byte, so at times, will need further processing... but thanks for the thought..	[reply]