RinstrX returns an index (for use with file extensions)

[HSE]

More than obvious 

[jj2007]

.jpeg and .json files are very common now. Is the point necessary?

No. Exactly here. Perhaps you don't have an answer.

Oh... now I get it: "point"="dot". So you mean this case:

Code Select Expand

  test ecx, RinstrX("This is a test.json", 1, .xls, .mdb, .json, .wk)
  inkey str$(eax), " is the index by RinstrX", 13, 10
Is the dot necessary?

Code Select Expand

test ecx, RinstrX("C:\XlsJsonJpegEtcFolder\MyFoto.jpeg", 1, .xls, .mdb, .Json, .Jpeg, .wk)
Guess what it would return without the dot...

[HSE]

Oh... now I get it: "point"="dot".

D**m. But perfectly valid in pseudo-english   

Is the dot necessary?

Ok. Perhaps English problem too. Look like, including the "dot", RinstrX is not so useful in 32 bits. Is posible to make modifications to recognice 4 characters instead of 3?

[jj2007]

Is posible to make modifications to recognice 4 characters instead of 3?

No need to modify the RinstrX macro

test ecx, RinstrX("C:\HectorsFiles\MyFoto.HSEpic", 1, .xls, .hsepic, .mdb, .Json, .Jpeg, .wk)
js NoSuchExtension

Returns index 1 (the "1" before .xls sets case-insensitive mode).

[HSE]

RinstrX("file1.xlsx",1,.xls,.xlsx,.doc,.docx,.htm,.html)  ?

[jj2007]

Code Select Expand

  test ecx, RinstrX("file1.xslx",1,.xsl,.xslx,.doc,.docx,.htm,.html)
  print str$(eax), " is the mode 1 index by RinstrX", 13, 10
Works fine, as long as you respect the order first 3-byte, then 4-byte extension.

[TimoVJL]

a good point, as dot is just a dot and point have a larger meaning.

a small, round spot that is used in numbers to separate whole numbers from parts of numbers:

[jj2007]

a good point, as dot is just a dot

You've made your point, Timo

[HSE]

Works fine, as long as you respect the order first 3-byte, then 4-byte extension.

Perfect.


Sorry, I was thinking in super fast comparison:

Code Select Expand

mov eax, 'xlsx'
push eax
...
pop eax
.if eax == extension
  ...
.endif


[jj2007]

I was thinking in super fast comparison

Less reliable (see examples above), and I doubt you'd ever use it in a speed-critical innermost loop ;-)