#6 closed Bug (Rejected)
StringInStr not reporting error
| Reported by: | Volly | Owned by: | Jpm |
|---|---|---|---|
| Milestone: | Component: | AutoIt | |
| Version: | 3.2.10.0 | Severity: | |
| Keywords: | Cc: |
Description (last modified by Jon)
WHen using string in string, I made a mistake in the code. I did this:
$stendSSB = StringInStr($read,'td width="100%"',18)
With 18 in the casesence slot, I should have gotten a error saying the command was badly formatted. I got no error at all. I should have coded the line like thia:
$stendSSB = StringInStr($read,'td width="100%"',0,18)
Version of AudoIt being used:
3.2.10.0
Attachments (0)
Change History (8)
comment:1 Changed 16 years ago by volly
comment:2 Changed 16 years ago by Jpm
- Resolution set to rejected
- Status changed from new to closed
Nobug error is only reported on occurrence error as described in the doc
comment:3 Changed 16 years ago by Jon
- Description modified (diff)
comment:4 Changed 16 years ago by Jpm
- Resolution rejected deleted
- Status changed from closed to reopened
comment:5 Changed 16 years ago by Jpm
- Owner set to Jpm
- Status changed from reopened to assigned
comment:6 Changed 16 years ago by Jpm
- Resolution set to rejected
- Status changed from assigned to closed
comment:7 Changed 16 years ago by Volly
rejected...then reopened...then rejected....I'm not sure what is going on here. somewhat confusing. I just expected when I made the error when I tried the code, Scite would report the syntax error. no biggie if not addressed. I just wanted to make sure it was noted in the system. Thanks guys for looking into it.
comment:8 Changed 16 years ago by anonymous
I was of the opinion that the case sense param wasn't "0 or 1", it was "0 or <>0" (similar to false/true). Hence 18, while confusing, is a perfectly valid parameter.
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
Look in description field