https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=1167 Mihael Hategan <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #1 from Mihael Hategan <[email protected]> 2014-05-29 15:13:45 --- It used to be by design, and tc.data not accepting wildcards was also by design. The reasoning was that if swift was used in a web application that allowed a user to edit a swift script, this would allow arbitrary command execution. However, we already implemented wildcards in tc.data, so not allowing extensions is relatively pointless outside a restrictive environment. It is still possible to restrict the apps that can be run by removing wildcards from tc.data, so the current scheme should support both scenarios. That said, trunk has had support for arbitrary strings as apps. However, they need to be enclosed in double quotes: app (file o) simulation () { "simulate.sh" stdout=filename(o); } This should be documented. -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.