gb119

QUOTE(dannyt @ Feb 13 2007, 11:30 AM)

Hi,

I wonder if anyone could help please help me improve my labview with regard regular expressions.

[...]

I can see a way to implement this using multiple matchsub-string vi's each using the output of the previous one, but I feel if only i could get the correct pattern I could do it with only one matchsub-string vi.

I am using Labview version 7.0

Many years ago (well about 6) I wrote a vi that interfaced to the Perl Compatible Regular Expressions library for LabVIEW 5.1. It's downloadable from: http://www.crojack.org/labview/pcre-2.08-lv.zip If you're running Windows then there is a precompiled binary, otherwise it's a question of compiling the CIN and linking to a version of libpcre. Basicallly my routine does the same as the one now builtin in LV 8.0+ - except that I did it first and mine isn't a nice extending node but can handle variable numbers of sub-patterns at run time. It's a long time since I used that version (I rolled the CIN code into a custom dll full of other useful code functions, and the PCRE version is positively prehistoric in internet terms !) so I can't promise that it all still works....

Google is your friend... http://www.sullutions.com/LabVIEW/Info-LabVIEW.html confirms that info-labview is currently down, although the machine itself seems to be up. I guess we're waiting for Scott Hannahs to perform the correct magic.

The key to scripting in LabVIEW 8.x can be deduced from the following statement:

Scripting features are exposed in LabVIEW <= 7.1, and

scripting features allow you to write LabVIEW code, and

scripting features are LabVIEW code, and

LabVIEW code that calls scripting features will run in later versions of LabVIEW.

Thanks - that was pretty much what I was I had figured out. Perhaps this could be added to the sticky post at the top of the forum ?

I'm sure this must be a FAQ, but if is then I've failed to find where it is answered:

How does one reveal the scripting methods and properties in LabVIEW 8.20 ? The ini key setting that works in LabVIEW 7.1 (SuperPrivateScriptingFeatureVisible=True) doesn't seem to have any effect for me and doesn't appear in the LabVIEW executable file. SuperSecretPrivateSpecialStuff=True does work (and is in the executable). This is for Windows FDS if that is relevant.

Gavin