Arc Forumnew | comments | leaders | submitlogin
7 points by bOR_ 5853 days ago | link | parent

Just in general - is there anything in arc which gives it a big edge to programmers when compared to clojure?

Here are some of the differences, but I can't tell if one of them is crucial. I listed three below for which I've no clue what the impact is.

  http://clojure.org/lisps
  * The read table is currently not accessible to user programs
  * Keywords are not Symbols
  * Symbols are not storage locations (see Var)
  * immutable data and first-class functions
  * *first* is clojure's *car* ;)


6 points by almkglor 5853 days ago | link

> Just in general - is there anything in arc which gives it a big edge to programmers when compared to clojure?

Mutation. It's one thing to allow functional programming. It's another thing to force it.

The only thing constant is change.

> * The read table is currently not accessible to user programs

Neither does Arc, although Anarki does allow redefining of 'ssyntax and 'ssexpand, which almost gives you the same thing.

IMO not giving access to the read table is a good thing. There are very subtle problems with this, starting with: the read table affects all code loaded after the readtable modification.

It affects them whether or not the code was written by you, and whether or not it was written with that readtable definition in mind.

This can cause unfortunate library breakage when two libraries try to modify the same readtable entry; the poor user is thus left at the mercy of which library loaded last.

In fact Arc-F has revoked Anarki's feature which allows 'ssyntax and 'ssexpand to be modified; redefine them all you want, Arc-F will use the built-in traditional 4 ssyntaxes : ~ ! .

HOWEVER, there are currently two reserved context metacommands which will eventually allow ssyntax redefinition at the level of the individual file: 'import-ssyntax and 'interface-ssyntax.

The important thing is that they are context-based, and because they are context-based, they are not global and they will (in general) affect only one loaded file.

> * Keywords are not Symbols

Unimportant - salt to taste.

> * Symbols are not storage locations (see Var) > * immutable data

Side effect (LOL) of the enforced FP.

> * first is clojure's car ;)

Unimportant - salt to taste

-----

1 point by bOR_ 5853 days ago | link

Thanks for the answer. I'll try, play and see how immutability affects me.

-----

6 points by almkglor 5853 days ago | link

Oh, Clojure is not quite completely immutable. Clojure has refs, and they can be mutated within the context of a 'dosync form. Kind of like the Haskell "do" syntax. It's more that Clojure defaults to immutability, and has special syntax to define portions that are imperative.

-----