I have some questions

[Ragias]

Hi , I am interesting about Loop

However , I dont understand

1) What connection does  Loop has with Lisp ? (is it about macros ?)
2) What is the performance penalties (can you compare it with clojure ? on runtime and start-up) ?
3) Can you put some examples in "http://rosettacode.org/"

[Dhanji R. Prasanna]

On Fri, Jul 6, 2012 at 6:01 PM, Ragias <rmanol...@hotmail.com> wrote:

Hi , I am interesting about Loop

However , I dont understand

1) What connection does  Loop has with Lisp ? (is it about macros ?)

It is a functional language, so it bears a lot of design similarities to Scheme (a popular Lisp). Here is a short article on infoq:

www.infoq.com/news/2012/07/loop-jvm-language

 

2) What is the performance penalties (can you compare it with clojure ? on runtime and start-up) ?

It's pretty fast. Since loop is not interpreted it is incredibly fast compared to most interpreted langs. Check out the article for info about startup times. Loop starts up almost as fast as the java runtime will allow.

 

3) Can you put some examples in "http://rosettacode.org/"

Cool, if I have time I would do it--I would love if you could as well, as you learn it. Here are some good examples:

https://github.com/dhanji/loop/tree/master/test/loop/confidence/algorithms

Dhanji.

[Ragias]

So it does not have macros.
but anyway ... i always liked functional programming with simple syntax

my only problem is the same that i had with clojure

In clojure you have to write (let []) and in Loop you have to write Where
I mean , I would like to write

flow(str) ->
  print(str),
  str2 : 'Lalala' ,
  print(str2)

other than that it looks promising

However keep the syntax simple ... or else you will end up like Scala

Another mistake of Scala is sbt ... if you can make Loop build tool like lein.
I will try to help

Also is it possible to make Loop compiled like Haskell ?
So it can check the types before running  all the functions ?

[Dhanji R. Prasanna]

Thanks for the nice words, yea will try and keep things simple. =)

The where blocks are not too much trouble I think, as they encourage you to write more functionally and use fewer variables. So overall a good balance.

Optional static typing is possible, as the parser does support type annotations on arguments. But this requires writing some pretty hairy type-checking code. It would be fun to write if you want to have a crack at it.