Plan for WildcardLISP

[microlith57]

• Should we interpolate in server or client?
• /@(?'lisp'\((?>(?1)|[a-z0-9@]| )*\))/i

LISP_REGEX = /@(?'lisp'\((?>(?1)|[a-z0-9@]| )*\))/i
# ...
parameter.gsub! LISP_REGEX do |match|
  # do WildcardLISP magic here; return interpolated result
end

[microlith57]

More thoughts:

• Interpolate only on client
• !(lisp) -> evaluate immediately
  • Then ! character implies urgency/immediacy so is good for 'evaluate-now' behaviour
  • Maybe in triggers have something like so:

trigger use @(exec 'create a !(+ "large" " " "teapot")')
use the machine
-> @(exec 'create a !(+ "large" " " "teapot")')
-> create a !(+ "large" " " "teapot")
-> create a large teapot

• Triggers act normally
  • Now multiple / vessel
  • Programs replaced with @exec wildcard which runs actions
  • Example of a program-like trigger above
• @(lisp) -> evaluate every read (eg in trigger / name / note etc.)
  • The @ character should stay with this behaviour as this is how it has always worked

@neauoire Any thoughts?

[microlith57]

Updated regex:

/(?'type'[@!])(?'lisp'\((?>(?2)|[a-z0-9@]| )*\))/i

However need to come up with list of allowed characters.