Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

le

Name: Anonymous 2013-08-15 19:02

I wish languages let you choose infix, postfix, or prefix freely.

Name: Anonymous 2013-08-15 21:11

Scheme does. There's a macro out there that can turn expressions into infix. Postfix is probably easier since there are no priorities. Just go through the list and push it onto a stack if it's a value or call it if it's a procedure.
(infix 3 + 5 * 2) becomes (+ 3 (* 5 2))

Name: Anonymous 2013-08-15 21:29

why? prefix is best.

Name: Anonymous 2013-08-15 21:56

>>3
Some people read and perform better in Postfix (e.g. computers, Asians)

Name: Anonymous 2013-08-15 22:27

>>3
Prove it.

Name: Anonymous 2013-08-16 0:51

keywords: Mixfix, Agda

Name: Anonymous 2013-08-16 1:49

>>5
Lisp.

Name: Anonymous 2013-08-16 2:06

>>7

versus what, forth?

Name: Anonymous 2013-08-16 3:00

>>7
>>8
Lisp and Forth are not enemies.

Name: Anonymous 2013-08-16 4:27

>>9
Did someone say REBOL?

Name: Anonymous 2013-08-16 15:33

>>10
No, I don't believe anyone did.

Name: Anonymous 2013-08-16 15:57

REBOL

Name: Anonymous 2013-08-16 18:23

>>3
In my opinion OOP has demonstrated that postfix/infix can be more easily read and shows transformation of data with the method chaining. You can simply read left to right.

e.g


[1,2,3].map(x => x * 2).filter(x => x > 2).forEach(print)


In contrast, prefix form.


forEach(print, filter(map([1,2,3], x => x * 2), x => x > 2))

Name: Anonymous 2013-08-16 21:25

>>13
I guess OOP also managed to fuck up notation too.

Name: Anonymous 2013-08-16 21:29

>>13
Terrible !

Name: Anonymous 2013-08-16 21:30

>>15
Awww, /g/arba/g/e-kun learned his first e/g/in /pro/g// meme!

Name: Anonymous 2013-08-16 22:58

>>13
Nikita, you truly are a goy.

Don't change these.
Name: Email:
Entire Thread Thread List