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

<< and >> for I/O

Name: Anonymous 2014-03-15 17:47

The use of << and >> for I/O came from Algol 68's "record transfer" extension.
http://archive.computerhistory.org/resources/text/algol/ACM_Algol_bulletin/1061601/p26-naur.pdf

Name: Anonymous 2014-03-16 2:41

Nope sorry it was just Straußtrup trying to be clever+cute. Any claim elsewise is revisionism.

Name: Anonymous 2014-03-16 5:19

But >> is used in any monad, not just in IO.

m >> k = m >>= (\_ -> k)

Name: Anonymous 2014-03-16 8:06

>>2
>le pedophile sage

Name: Anonymous 2014-03-18 6:57

Python 3.4 released, you now divide paths to concatenate them, because "it looks like a path separator".

Good job, Guido van Stroostruup!

Name: Anonymous 2014-03-18 9:16

I never used bit wise operators much anyway.

Name: Anonymous 2014-03-20 17:44

PRIO >> = 1, << = 1;

OP >> = (REF FILE f, SIMPLIN s)REF FILE: (get(f, s); f),

   << = (REF FILE f, SIMPLOUT s)REF FILE: (put(f, s); f);

Name: Anonymous 2014-03-21 9:42

IO
not pure!

Name: Anonymous 2014-03-21 13:14

>>8
At least it's explicit. Most languages don't have even that. In those languages every piece of code could do anything, from downloading child porn to launching nuclear missiles.

Name: Anonymous 2014-03-21 13:50

>>9
downloading child porn to launching nuclear missiles
not pure!

Newer Posts

<< and >> for I/O

1 Name: Anonymous 2014-03-15 17:47

2 Name: Anonymous 2014-03-16 2:41

3 Name: Anonymous 2014-03-16 5:19

4 Name: Anonymous 2014-03-16 8:06

5 Name: Anonymous 2014-03-18 6:57

6 Name: Anonymous 2014-03-18 9:16

7 Name: Anonymous 2014-03-20 17:44

8 Name: Anonymous 2014-03-21 9:42

9 Name: Anonymous 2014-03-21 13:14

10 Name: Anonymous 2014-03-21 13:50