On Apr 5, 2009, at 9:34 PM, john skaller wrote:
> At this point some choices need to be made about lvalue stuff. In
> principle
> the idea is:
>
> a) a var is actually a pointer
> b) mutation including assignment requires a pointer
> c) offset can be added to pointers to support mutation of sub
On Apr 5, 2009, at 11:21 PM, john skaller wrote:
>
>
> On 06/04/2009, at 3:51 PM, Erick Tryzelaar wrote:
>
>>> git clone felix...@felix-lang.org:felix
>
>
> U also need to say:
>
> git submodule update --init
>
> to get ocs, tre etc ..
Sorry about that. Which version of git do you have? I think
On 06/04/2009, at 3:51 PM, Erick Tryzelaar wrote:
>> git clone felix...@felix-lang.org:felix
U also need to say:
git submodule update --init
to get ocs, tre etc ..
--
john skaller
skal...@users.sourceforge.net
-
Good evening/morning/afternoon. So once everyone gets me their ssh public key
you can start developing on felix. The instructions are slightly different than
for the read only access. You will need to use this pattern:
{{{
> git clone felix...@felix-lang.org:$NAME
}}}
Like this:
{{{
> git clon
The second problem that needs addressing is what to do with closures.
In an FPL, a function value is immutable and execution puts the program
counter on the stack, and values constructed on the stack or heap.
In Felix, procedure values are not immutable: the closure objects
contain
local variab
At this point some choices need to be made about lvalue stuff. In
principle
the idea is:
a) a var is actually a pointer
b) mutation including assignment requires a pointer
c) offset can be added to pointers to support mutation of sub components
The question is what 'x' means given
var
We've decided to finally migrate our repository to git, which you can find
[here](http://git.felix-lang.org). To checkout the read-only copy, do:
> git clone http://git.felix-lang.org/r/felix.git
Developers, if you've got any outstanding subversion patches, please migrate
them over to the git r
2009/4/4 john skaller
>
> On 05/04/2009, at 3:18 AM, Emmanuel Onzon wrote:
>
>
>> Well computers can't "guess" .. so we need some rules and
>> ways to break out.
>>
>> You can do inference with the available information. The same
>> information that makes you able to know which Obj_*
>> construct
