LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Search string array for string subset containing special characters

Solved!
Go to solution

@billko wrote:

 

And I forgot that Booleans aren't truly one bit; it actually takes 8 bits to represent each Boolean so thanks for reminding me about that.

It used to be even a 16-bit integer until LabVIEW 4.x. But boolean arrays were packed with 8 boolean values per byte. But that was changed in LabVIEW 5.0 because the packed boolean array was memory conserving but very CPU intense to pack/unpack and index.

Rolf Kalbermatter
My Blog
Message 11 of 16
(176 Views)

@rolfk wrote:

@billko wrote:

 

And I forgot that Booleans aren't truly one bit; it actually takes 8 bits to represent each Boolean so thanks for reminding me about that.

It used to be even a 16-bit integer until LabVIEW 4.x. But boolean arrays were packed with 8 boolean values per byte. But that was changed in LabVIEW 5.0 because the packed boolean array was memory conserving but very CPU intense to pack/unpack and index.


Did you have 8 booleans in 16 bits?

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 12 of 16
(133 Views)

@rolfk wrote:

...  until LabVIEW 4.x. But boolean arrays were packed with 8 boolean values per byte. But that was changed in LabVIEW 5.0 because the packed boolean array was memory conserving but very CPU intense to pack/unpack and index.

 

A side effect is that we still have that overlooked 4.x typecast mode that can be sometimes useful, but we need to remember that the index 0 is the MSB.

 

altenbach_0-1743692372436.png

 

Message 13 of 16
(126 Views)

@Yamaeda wrote:

@rolfk wrote:

@billko wrote:

 

And I forgot that Booleans aren't truly one bit; it actually takes 8 bits to represent each Boolean so thanks for reminding me about that.

It used to be even a 16-bit integer until LabVIEW 4.x. But boolean arrays were packed with 8 boolean values per byte. But that was changed in LabVIEW 5.0 because the packed boolean array was memory conserving but very CPU intense to pack/unpack and index.


Did you have 8 booleans in 16 bits?


No. A scalar boolean was an int16 and an array of booleans was 16 bit padded.

Rolf Kalbermatter
My Blog
Message 14 of 16
(106 Views)

@rolfk wrote:
A scalar boolean was an int16 and an array of booleans was 16 bit padded.

Here's the proof that a scalar boolean was 2 bytes.

 

 

altenbach_1-1743750622855.png

 

Message 15 of 16
(82 Views)

Cool. I like learning of the history, i first touched LV in ver 5 i think (very rudimental) and any form of advanced LV was 8.2 for me.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 16 of 16
(70 Views)