Author Topic: Axe Parser (Read 551824 times)

samebull (metagross111) · « **Reply #1860 on:** July 05, 2011, 08:22:16 am »

Quote from: Art_of_camelot on July 05, 2011, 08:05:15 am

Actually it is listed there in small font. It said lambdas. Which was also mentioned by other posters on this page of this thread. I'm not even sure why you thought it would be necessary to turn off image blocker anyway, you can click through the spoilers and still read what it says without even messing with image blocker.

*edit*: Ok, it gives alternate text with image blocker on... how strange.

I had to zoom in my browser a zillion times to see that word. then I reasoned the pics might have been screenshots or something. allow images, add water and BOOM, instant headaches with half that screen flashing. It wouldn't have been an issue if I hadn't just zoomed in a couple dozen times.

I was warned of this too in my intro topic.

Deep Toaster · « **Reply #1861 on:** July 05, 2011, 06:12:58 pm »

Quote from: Quigibo on July 05, 2011, 01:50:45 am

I don't think it will ever be "Finished". Its going to stay alive for a long time, the 1.0.0 will just be the largest, most improved, programming-style changing update to date. If I ever fear the Parser is starting to die due to real life stuff or boredom of working on the same project for so long, I will definitely pass it on to another programmer to continue, I wouldn't leave you guys hanging.

Perpetual betas are awesome

Good luck on 1.0.

ZippyDee · « **Reply #1862 on:** July 05, 2011, 06:14:48 pm »

Quote from: samebull on July 05, 2011, 08:22:16 am

Quote from: Art_of_camelot on July 05, 2011, 08:05:15 am
Actually it is listed there in small font. It said lambdas. Which was also mentioned by other posters on this page of this thread. I'm not even sure why you thought it would be necessary to turn off image blocker anyway, you can click through the spoilers and still read what it says without even messing with image blocker.

*edit*: Ok, it gives alternate text with image blocker on... how strange.

I had to zoom in my browser a zillion times to see that word. then I reasoned the pics might have been screenshots or something. allow images, add water and BOOM, instant headaches with half that screen flashing. It wouldn't have been an issue if I hadn't just zoomed in a couple dozen times.

I was warned of this too in my intro topic.

Maybe madly flashing smileys aren't the best idea! (I don't really like them much myself...)

Compynerd255 · « **Reply #1863 on:** July 06, 2011, 08:03:29 pm »

Okay, lambdas are freakin' cool! I can't wait to use them in Axe, although I'm trying to think about how I would... I do know that one of my dad's programs uses lambdas to pass drawing routines for different objects into a positioning routine.

Darl181 · « **Reply #1864 on:** July 07, 2011, 08:10:34 am »

Quote from: Ashbad on July 02, 2011, 01:07:12 pm

Quote from: calcdude84se on July 02, 2011, 01:02:39 pm
More seriously, Ashbad's referring to inline functions, I presume, which probably aren't going to happen.

Quigibo just said they were gonna happen, so I assume they are

Ok, let me rephrase that.

Can someone describe in simple(r) english what lambdas are and how they are used?

leafy · « **Reply #1865 on:** July 07, 2011, 11:41:26 am »

Lambdas are interesting programming solutions to difficult problems. I've used them in Python before.

Deep Toaster · « **Reply #1866 on:** July 07, 2011, 11:43:27 am »

I just realized... Lambdas are basically routines you pass around like arguments, right? I actually need that

Good luck on it!

GreenFreak · « **Reply #1867 on:** July 08, 2011, 07:08:49 am »

I don't understand that...

When should I use lambdas?

Deep Toaster · « **Reply #1868 on:** July 08, 2011, 01:52:00 pm »

If you're making a falldown game, for instance, where every level comes with a special feature (bouncing, antigravity, whatever), you can make each feature a lambda and pass it to the game.

Ashbad · « **Reply #1869 on:** July 08, 2011, 02:16:14 pm »

Well, as someone who uses them all the time in programming, I can say they are very useful in many situations. They can help reduce the number of methods needed to evaluate a certain value. DeepThought gives a decent example with different features per level, such as if you had two different levels of gravity:

Code: [Select]

@gravity = lambda {|cur_level|(cur_level%5==0)?(1):(2)} / air_density
So that every five levels the lambda would return 2 instead of 1. In that example you could take out the lambda and still be fine, but there are even bigger needs for it when you need to directly pass values as parameters into complex equations with highly varying outputs or when you go to attach them to variables directly so that a variable's state is defined by input parameters. Which brings me to ask, quigibo: are you thinking of adding full support for lambdas/procs with variable attachments and inlining functions, or just inlining?

EDIT: hmm, so the case here isn't just that many don't know how to use them, but that they also don't know what they are

understandable. In a nutshell:

Lambdas are functions that stand in for single values (though in some cases they can return multiple values, but don't worry about that most languages don't even support it). They can take passed arguments and can contain code that'll evaluate expressions and return values accordingly. Very, very useful. For a decent background, here's the wikipedia link Qwerty pointed me to a long time ago that I found very helpful: http://en.wikipedia.org/wiki/Lambda_calculus

GreenFreak · « **Reply #1870 on:** July 08, 2011, 02:31:34 pm »

ookaaay...
That sounds really useful

But I don't understand the code

Code: [Select]

@gravity = lambda {|cur_level|(cur_level%5==0)?(1):(2)} / air_density
EDIT: your EDIT helped me to understand it better! thanks

Ashbad · « **Reply #1871 on:** July 08, 2011, 02:37:40 pm »

Simpler variant:

Code: [Select]

if cur_level%5 == 0
  Thing = 1
else
  Thing = 2
end
Gravity = Thing / air_density

Quigibo · « **Reply #1872 on:** July 08, 2011, 02:43:17 pm »

Fine! I'll give an example since people seem to be confused...

Map(λ(r₁²),L₁,100)

If you made a function map (which functional programmers should recognize) this would square the first 100 numbers of L1. You could pass any function there, this example is a function of 1 argument. But in general, lambda expressions are functions of r1-r6 depending on how many arguments the function is expecting. Its as if you had made a label in your code "Lbl A:Return r₁²" and then passed _LA (the address of the function) as the argument. But here you don't need to assign it a label name... sort of like inline data.

Ashbad · « **Reply #1873 on:** July 08, 2011, 02:47:49 pm »

* Ashbad pays off people who didn't understand since they allowed him to finally see Axe's implementation

EDIT: hmm.. Your implementation is similar to haskell's or lisp's implementation, as more of a higher order function rather than a general purpose value stand in or an attached proc that directly manipulates a variable's value upon accessing. Anyways, cool, this would be very useful to me in many circumstances, and I guess you can't really implement the pythonic/Rubonic version in axe anyways

it'd be a bit impracticable

GreenFreak · « **Reply #1874 on:** July 08, 2011, 03:12:03 pm »

Quote from: Ashbad on July 08, 2011, 02:47:49 pm

* Ashbad pays off people who didn't understand since they allowed him to finally see Axe's implementation

I hope, you'll explain that in the Axe-documentation, Quigibo
Because I'm still confused a bit^^

Author Topic: Axe Parser (Read 551824 times)

samebull (metagross111)

Re: Axe Parser

Deep Toaster

Re: Axe Parser

ZippyDee

Re: Axe Parser

Compynerd255

Re: Axe Parser

Darl181

Re: Axe Parser

leafy

Re: Axe Parser

Deep Toaster

Re: Axe Parser

GreenFreak

Re: Axe Parser

Deep Toaster

Re: Axe Parser

Ashbad

Re: Axe Parser

GreenFreak

Re: Axe Parser

Ashbad

Re: Axe Parser

Quigibo

Re: Axe Parser

Ashbad

Re: Axe Parser

GreenFreak

Re: Axe Parser