Just a suggestion, Mark - instead of L.DoString(string(file)) in response to a failure on L.DoFile (is there no other error that can occur there other than the file being missing?), do an explicit test for the file existing, and if it does not exist, grab the asset from bindata and *write it out* - then do your L.DoFile.
While it may not seem much of a change, it means that as soon as your program runs, whatever scripts it needs get punted out onto the file system where your end user can see and fiddle with them. Depending on your intentions, your way may be more appropriate (e.g. you only want the dynamicism to support updates rather than end-user tinkering), but this method is more discoverable if end-user tweaking is permissible. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/58faabde-82a0-43da-b88d-cda4a94bdb36%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
