public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: list+org.sourceware.kawa@io7m.com
To: kawa@sourceware.org
Subject: Are types checked statically?
Date: Thu, 16 Mar 2017 17:02:00 -0000	[thread overview]
Message-ID: <20170316170239.2e6b55d0@copperhead.int.arc7.info> (raw)

[-- Attachment #1: Type: text/plain, Size: 637 bytes --]

Hello!

I'm looking for a scripting language that can be embedded into a Java
program (ideally via the JSR223 API, but this is not a hard
requirement). However, one of my requirements is static type checking
and that tends to limit the options somewhat. As someone who enjoys
functional programming, I was quite pleased to learn that Kawa existed!
However, I can't quite make out from the information on the site
whether or not the types are checked at compilation time or not. I 
appreciate that the distinction is somewhat subtle if "compilation
time" actually means "when the script is loaded by the running program".

M

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]

             reply	other threads:[~2017-03-16 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 17:02 list+org.sourceware.kawa [this message]
2017-03-16 17:23 ` Per Bothner
2017-03-16 17:39   ` list+org.sourceware.kawa
2017-03-16 22:57     ` Per Bothner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170316170239.2e6b55d0@copperhead.int.arc7.info \
    --to=list+org.sourceware.kawa@io7m.com \
    --cc=kawa@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).