Dear Jan,
a way to go would be to use SML to JS, a Standard ML to JavaScript 
compiler:
https://github.com/melsman/mlkit/blob/master/README_SMLTOJS
Would you be interested in doing experiments using this?
Best
- Gergely
2017-03-11 19:06 időpontban jan ezt írta:
Hello,
I am also on my way to learn to write extensions (hopefully) -
currently, I am using Javascript to learn it.
While not a typical functional language (like Haskell or Lisp), it has
many functional features (historically inspired by Self and Scheme),
lambda, currying, younameit... works pretty well and there are many
libraries which extend it further in this direction. There are also 
some
numerical and statistical libraries for it.
The syntax looks sadly rather differently than ML (which is only
superficial, but still has an effect at least on me).
Jan
Am 11.03.2017 um 15:45 schrieb Heiko Tietze: There is also a Delphi 
binding at https://sourceforge.net/projects/uno-pas-bridge/. 
Unfortunately it wasn't updated for years and a quick test with 
Freepascal failed.
On 02/16/2017 11:28 AM, Stephan Bergmann wrote: On 02/15/2017 12:12 PM, 
Gergely Buday wrote: I am interested in writing an extension to Libre 
Office,
particularly Calc.
I would like to do it in a functional language.
 [SNIP]
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Context
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.