Arc/Nu is Lite Nu + other features. At the time of this post, those additional features include:
* redef/remac/extend
* defcall
* `var` for accessing global variables (I will probably change the name)
* implicit parameters
* utilities for inspecting/manipulating paths, such as cwd, dirname, basename, etc.
* an `import` macro for easily loading files
There are also some libraries in the lib/ subdirectory, and applications I've written in the app/ subdirectory.
---
Why yet another branch on GitHub? I have three major projects right now:
1. The Nu compiler, which is used for Lite Nu and Arc/Nu. It's intended to be very compatible with Arc 3.1 while fixing bugs and making it possible to add additional features.
2. Arubic, which is my language based loosely on Arc.
3. arc2js which intends to allow you to execute Arc/Arubic code in the browser.
To put it another way, the three projects are essentially: Arc 3.1, Arubic, and JS. Arc/Nu is a part of project #1, but I got tired of implementing Arubic and arc2js, so I decided to add some convenience libraries on top of Lite Nu, which is a lot easier to do.
So now project #1 is split into two separate sub-projects: Lite Nu and Arc/Nu. Lite Nu is for people who just want Arc 3.1, period. No conveniences, no new features. Just Arc 3.1. Arc/Nu is for people who want Arc 3.1, but also want some shiny new features.
Just a suggestion, though I'm not sure what work it will involve: fwiw, why don't you let Arc/Nu be the pure Arc version and lite-nu be the extended version. The name Arc/Nu better reflects the closeness to Arc itself.
Great job on the two - I enjoyed testing and writing them up on Arc Lang Wiki. : )
Because "lite" implies a lacking of something. I'm not entirely against changing the names, but simply swapping them won't work. Anybody have any suggestions for a name for the more "full featured" version of Nu?
Thanks, Rocketnia. I had actually placed each pair on its own line with a carriage return, but the text editor kept removing it upon posting.
I came up with this list keeping Arc/Nu as the proposed name for the pure Arc implementation, and then was left with the '/Nu' slice as the only way to keep the product association. So that left only the Arc component to play with. My personal preference is ax/nu: a -> Arc and x -> extended. Ax/Nu also has the benefit of brevity, IMHO.
