LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Darren's Occasional Nugget 09/26/2022

Here's one even faster.  Might be the fastest in this topic yet. (optimized XML un-escape)

 

Message 31 of 53
(2,500 Views)

@Ettepet wrote:

Here's one even faster.  Might be the fastest in this topic yet. (optimized XML un-escape)

 


I don't see much difference in timing:

 

Ettepet (fastest)= 0.180248
Darren = 0.179282
Ooth = 0.194544

 

But there does seem to be a problem with Ooth's implementation.

Frozen_0-1668782518021.png

 

BTW. I am not a fan of your "compressed" coding style and would never use it as-is. 😱

 

---------------------------------------------
Certified LabVIEW Developer (CLD)
0 Kudos
Message 32 of 53
(2,442 Views)

@Frozen wrote:

BTW. I am not a fan of your "compressed" coding style and would never use it as-is. 😱

 


Shorter wires means the electrons flow faster, and have less resistance, making the program run faster.

 

Spoiler
This is a joke, please don't do this thinking it will make it run faster.
Message 33 of 53
(2,436 Views)

"Electrons"?  I thought they were datons.

"If you weren't supposed to push it, it wouldn't be a button."
Message 34 of 53
(2,411 Views)

BTW. I am not a fan of your "compressed" coding style and would never use it as-is. 😱

 


I prefer to have my code fit on a normal pc screen (more or less), not 3 or 4 screens wide. 😆

 

Thanks for the timing comparison!

 

Darren's solution probably is a bit quicker because it doesn't do XML-unescape or regional number-formatting.  Couldn't tell from the "protected" code he uploaded. 🙂

0 Kudos
Message 35 of 53
(2,411 Views)

@Ettepet wrote:

Darren's solution probably is a bit quicker because it doesn't do XML-unescape or regional number-formatting.  Couldn't tell from the "protected" code he uploaded. 🙂


I only uploaded one VI, in my original post. It was documented and not password-protected.

0 Kudos
Message 36 of 53
(2,400 Views)

@Darren wrote:

@Ettepet wrote:

Darren's solution probably is a bit quicker because it doesn't do XML-unescape or regional number-formatting.  Couldn't tell from the "protected" code he uploaded. 🙂


I only uploaded one VI, in my original post. It was documented and not password-protected.


Sorry for that, end of the day.  Thanks for your original code b.t.w.  I can now have Excel files open in Excel while importing data, which is a great help.

 

...so that means its slightly faster time comes from not doing XML-escaping, regional-number formatting etc.

0 Kudos
Message 37 of 53
(2,373 Views)

Anyone opposed to me turning a version into a VIPM package? I presume DNatt doesn't mind if I start from his, want to check with others. I would link to this forum in the package description.

0 Kudos
Message 38 of 53
(2,017 Views)

@DerrickB wrote:

Anyone opposed to me turning a version into a VIPM package? I presume DNatt doesn't mind if I start from his, want to check with others. I would link to this forum in the package description.


Sounds great, thanks for doing this Derrick. My preference would be that you use my original VI (I did not see anybody report any bugs with the original version in this thread), and credit me as the author.

0 Kudos
Message 39 of 53
(2,011 Views)

@Darren wrote:

@DerrickB wrote:

Anyone opposed to me turning a version into a VIPM package? I presume DNatt doesn't mind if I start from his, want to check with others. I would link to this forum in the package description.


Sounds great, thanks for doing this Derrick. My preference would be that you use my original VI (I did not see anybody report any bugs with the original version in this thread), and credit me as the author.


If your original post does do XML-escaping, regional-number formatting etc. you would be correct.  If it doesn't you would need to correct that.

 

I will continue to use mine, which also has some efficiency improvements and fits on my display.

0 Kudos
Message 40 of 53
(1,967 Views)