On 26 June 2012 08:58, Justin Clark-Casey <[email protected]> wrote: > I don't like the way script language/desired engine detection was done - a > clash with existing scripts could have been avoided by requiring some > special preceeding chracters rather than simple c#, lsl:DotNetEngine, etc > (like #! in shell scripts, for instance).
Agreed, but on the assumption that we're stuck with this convention now, would it be possible to tighten up the pattern matching a bit? It feels like the system should be able to tell the difference between //c# ...and // This is a comment consisting of multiple words. What it has to do with script engines: Nothing. Just checking for a colon seems a bit broad. One of the mind-numbing busywork tasks on my TODO list this morning is cleaning up some scripts somebody checked in since I last fixed our iar. Their editor - I think it's the Eclipse plugin - has helpfully added: // LSL script generated: furniture-1.0.object_definitions.presentation_seating.lslp Sat Nov 19 14:36:29 Tokyo Standard Time 2011 -- Edmund Edgar Avatar Classroom Your classroom, on the web, in a virtual world. [email protected] +81 090 3912 3380 Skype: edmundedgar Second Life: Edmund Earp Linked In: edmundedgar Twitter: @edmundedgar http://www.avatarclassroom.com _______________________________________________ Opensim-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-users
