Modify

Opened 16 years ago

Closed 16 years ago

#1174 closed Bug (No Bug)

Fatal Error when "bad" code sent to Execute() function

Reported by: autoit@… Owned by:
Milestone: Component: AutoIt
Version: 3.3.0.0 Severity: None
Keywords: Execute fatal error Cc:

Description

In older versions, if the Execute function was passed a "bad" string to execute, it would just return "" and set @error=1. Ever since the RunErrorsFatal option was removed the Execute function returns a fatal error. I'm not asking to reinstate the option, just please stop the execute from producing a fatal error. (And no, it isn't that simple for me to determine if the string passed into the Execute is valid since it is user-defined. :)

Here is a real quick sample:

Local $f=Execute("<div>Hello World</div>")
Msgbox(0,"",$f)

Attachments (0)

Change History (1)

comment:1 by Valik, 16 years ago

Resolution: No Bug
Status: newclosed

Err, okay. The RunErrorsFatal option had absolutely nothing to do with Execute. Further, the bug you describe does not happen with either 3.3.0.0 or 3.3.1.1. I suggest posting on the forum first in the future to ensure you really do have a bug.

Modify Ticket

Action
as closed The ticket will remain with no owner.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.