Some thoughts on scripting languages

1
Some thoughts on scripting languages

• Eric van Herwijnen
• Wednesday, 28 June 2000

2
Scripts (1)

• Creating special purpose commands
• everyone uses what they like best
• perl, python, javascript
• java less suited (cant give OS commands)
• CGI-scripts
• java (servlets)

3
Scripts, C

• For adding interactivity to frameworks, C
• java (see Stephans talk - JGAUDI), not ideal
• perl need to make an API (use SWIG to generate
  shadow classes, objects), new syntax
• python, API required, new syntax
• cint seems to be the default in HEP

4
SCRIPTS, cint

• CINT
• part of ROOT
• API backwards compatible
• standalone, no development required to integrate
  with GAUDI
• can make a dicitonary with makecint, compile
  link GAUDI with this dictionary, start cint, load
  shared library, then GAUDI classes available from
  cint
• kumac mode available
• macros
• have access to anything -gt makes ROOT crash...

5
SCRITPS, java

• For adding interactivity to java frameworks
• javascript
• java interpreters exist (dynamic java)
• jpython
• beanshell
• compile java on the fly (JAS does this)
• macros can easily be broken over time
• need to define an API to avoid this, only give
  things through an interface that stays fixed