/prog/ - Sepples is bad for your brain

Name: Anonymous 2014-12-12 21:11

Holy fuck, why are sepples coders so stupid

Note that instead of adding virtual methods to the ExprAST class hierarchy, it could also make sense to use a visitor pattern or some other way to model this. Again, this tutorial won’t dwell on good software engineering practices: for our purposes, adding a virtual method is simplest.
visitor pattern
good practices
bloated shit that exists only to mitigate the utter uselessness and weakness of COP
good practices

http://llvm.org/docs/tutorial/LangImpl3.html

Bring me that fucker so I can smash his balls and shove his bloody semen down his dipshit lying throat

Name: Anonymous 2014-12-14 3:42

>>14 is an IO nigger.

* (defgeneric foo ((obj1 class1) (obj2 class2)))

debugger invoked on a SB-INT:SIMPLE-PROGRAM-ERROR in thread
#<THREAD "main thread" RUNNING {AB1F741}>:
  Required argument is not a symbol: (OBJ1 CLASS1)

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT] Exit debugger, returning to top level.

((LAMBDA () :IN SB-C:COMPILER-ERROR))
0]

Sepples is bad for your brain

1 Name: Anonymous 2014-12-12 21:11

15 Name: Anonymous 2014-12-14 3:42

Name: Anonymous 2014-12-12 21:11

Name: Anonymous 2014-12-14 3:42