[Tutorial] Edition 2: Using Axe to its full functional form λ

[Quigibo]

Unfortunately I can't add an extra space to the token because of ReturnIf.  I don't think adding in a space is messy, and you can ignore the space if you want, its still valid.

[Ashbad]

Good point.  But I prefer the old style better even if it is valid the other way.

[LincolnB]

Plus, adding in your own spaces is something I find messy

Really? I think it's great unless you're trying to indent all of your if statements and loops were there's like thirteen nested layers

[Ashbad]

Plus, adding in your own spaces is something I find messy

Really? I think it's great unless you're trying to indent all of your if statements and loops were there's like thirteen nested layers

Well, I like to think of it as being a last equation -> outside world notation rather than a give equation notation.  I also like to think of Return as an end for a def statement, since explicit routines are only created with a label with no ending keyword, an adding something past that would make it feel akward.

[LincolnB]

Well, I like to think of it as being a last equation -> outside world notation rather than a give equation notation.

What in the world do you mean?

[Ashbad]

What I mean is that I think of returning values in Axe in a more functional way, so that the last expression is the overall output value for the entire function.  That way, I only use Return for ending the definition ending.

[LincolnB]

Oh, all right.

[ztrumpet]

What I mean is that I think of returning values in Axe in a more functional way, so that the last expression is the overall output value for the entire function.  That way, I only use Return for ending the definition ending.

Yeah, I tend to think of it this way as well.

[nemo]

quick question, what's the advantage of currying in axe? as runer pointed out, it takes up more memory, and in my opinion, looks messier

[Ashbad]

Well, depends on what form of currying you're talking about.  For non-pure-functional currying, its useful because it means in general that you're just passing parameters to explicit or non-explicit functions called or even defined and then called inside of the function.  For Haskellian currying, there is no definite use, unless you want to pass a very, very long list of parameters.

[selectcoaxial]

beginner question, how do you get r1 and r2 on the graphics calculator?

[mrmprog]

Vars->Y-Vars->Polar
Hope that helps.

[Ashbad]

You can have up to 6, using tokens r1-r6.

[Munchor]

A subroutine is called like:

Code: Select All | Copy To Clipboard

1	sub(DD, A, "HELLO", C, 5)

In this example, A is r1, "HELLO" is r2, C is r3, 5 is r4.

I once needed more arguments...

[Ashbad]

So, is this just going to never be in the new "Tutorials" section?  I've asked like 5 times in 3 separate threads, and I'm pretty much forced to give up all hope.  People who want to see this will have to follow the new "this is outdated link" in the old tutorial, I guess

Edit:

A subroutine is called like:

Code: Select All | Copy To Clipboard

1	sub(DD, A, "HELLO", C, 5)

In this example, A is r1, "HELLO" is r2, C is r3, 5 is r4.

I once needed more arguments...

On a side note here is a good example of where Haskellian currying would be put to good use.  Let's say you need 8 arguments.  You can always curry so to get some more parameters.

Code: Select All | Copy To Clipboard

1 2 3 4 5 6

(ADD8(1,2,3,4,5,6))(7,8) Lbl ADD8   r1+r2+r3+r4+r5+r6->r6   λ(r6+r1+r2) Return

Trivial example again, but shows essentially what I mean.  While this example contradicts it, I suggest you limit curried functions up to 5 parameters so that r6 can hood intermediate values between function followings.