Author Topic: LASTSPOKENCMD vs. CMDSEGMENT efficiency comparison  (Read 3411 times)

Exergist

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 405
  • Ride the lightning
LASTSPOKENCMD vs. CMDSEGMENT efficiency comparison
« on: March 01, 2017, 10:47:00 AM »
Can anyone comment about the processing efficiency of the following commands:

When I Say: Ashley [Marksman; Inferno Grenade; Concussive Shot; Disruptor Ammo]

Code: [Select]
Begin Text Compare : [{CMDSEGMENT:1}] Equals 'concussive shot'

versus...

Code: [Select]
Begin Text Compare : [{LASTSPOKENCMD}] Contains 'concussive shot'

If there is any appreciable difference I'd wager that using CMDSEGMENT is faster since it is searching (comparing) only a portion of the spoken command instead of the entire command.

Thoughts?

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 2824
Re: LASTSPOKENCMD vs. CMDSEGMENT efficiency comparison
« Reply #1 on: March 01, 2017, 11:01:38 AM »
There would be no humanly-detectable difference between those two statements.  If you were running that statement thousands of times in succession, you may see a very slight difference.

Exergist

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 405
  • Ride the lightning
Re: LASTSPOKENCMD vs. CMDSEGMENT efficiency comparison
« Reply #2 on: March 01, 2017, 01:10:10 PM »
Thanks for the info Gary!  :D