Modify ↓
Opened 16 years ago
Closed 16 years ago
#886 closed Bug (Fixed)
Make it explicit that operator == is a forced string comparison.
Reported by: | Valik | Owned by: | Valik |
---|---|---|---|
Milestone: | 3.3.1.0 | Component: | AutoIt |
Version: | 3.3.0.0 | Severity: | None |
Keywords: | Cc: |
Description (last modified by Valik)
It's ambiguous how operator == works. It needs to mention it is a forced string comparison. It currently implies that it behaves just like operator = except when comparing strings it's case sensitive. That is not true, it always compares as strings.
Attachments (0)
Change History (5)
comment:1 Changed 16 years ago by Valik
- Description modified (diff)
- Summary changed from Make it explicit that operator == is a force string comparison. to Make it explicit that operator == is a forced string comparison.
comment:2 Changed 16 years ago by Jpm
can you give us an example?
comment:3 Changed 16 years ago by Jpm
- Milestone set to 3.3.1.0
- Owner changed from Valik to Jpm
- Resolution set to Fixed
- Status changed from new to closed
Fixed in version: 3.3.1.0
comment:4 Changed 16 years ago by Valik
- Milestone 3.3.1.0 deleted
- Resolution Fixed deleted
- Status changed from closed to reopened
The documentation was not made any clearer, re-opening.
comment:5 Changed 16 years ago by Valik
- Milestone set to 3.3.1.0
- Owner changed from Jpm to Valik
- Resolution set to Fixed
- Status changed from reopened to closed
Fixed in version: 3.3.1.0
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.
Note: See
TracTickets for help on using
tickets.
Fixed silly typos.