Opened 15 years ago

Closed 15 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: Severity: None
Keywords: Execute fatal error Cc:


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>")

Attachments (0)

Change History (1)

comment:1 Changed 15 years ago by Valik

  • Resolution set to No Bug
  • Status changed from new to closed

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

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.

Add Comment

Modify Ticket

as closed The ticket will remain with no owner.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.