giahh Posted May 25, 2019 Share Posted May 25, 2019 Hello every one, I have a small question is: With a large amount of data, if I use StringSplit to convert it to Array then use ArrayFindAll to find or just leave it as a string and use StringInStr to find which is effective than? And the fastest? Thanks. Link to comment Share on other sites More sharing options...
BrewManNH Posted May 25, 2019 Share Posted May 25, 2019 How about you try both,or all of the choices you can think of, and report the results? Or do a search to see if its been done before and go from there? If I posted any code, assume that code was written using the latest release version unless stated otherwise. Also, if it doesn't work on XP I can't help with that because I don't have access to XP, and I'm not going to.Give a programmer the correct code and he can do his work for a day. Teach a programmer to debug and he can do his work for a lifetime - by Chirag GudeHow to ask questions the smart way! I hereby grant any person the right to use any code I post, that I am the original author of, on the autoitscript.com forums, unless I've specifically stated otherwise in the code or the thread post. If you do use my code all I ask, as a courtesy, is to make note of where you got it from. Back up and restore Windows user files _Array.au3 - Modified array functions that include support for 2D arrays. - ColorChooser - An add-on for SciTE that pops up a color dialog so you can select and paste a color code into a script. - Customizable Splashscreen GUI w/Progress Bar - Create a custom "splash screen" GUI with a progress bar and custom label. - _FileGetProperty - Retrieve the properties of a file - SciTE Toolbar - A toolbar demo for use with the SciTE editor - GUIRegisterMsg demo - Demo script to show how to use the Windows messages to interact with controls and your GUI. - Latin Square password generator Link to comment Share on other sites More sharing options...
Zedna Posted May 27, 2019 Share Posted May 27, 2019 As BrewManNH said + when using StringInStr() always (when possible) use CaseSense parametr set to $STR_CASESENSE (1) = case sensitive This is MUCH FASTER (especially on larger data) then default $STR_NOCASESENSE (0) Resources UDF ResourcesEx UDF AutoIt Forum Search Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now