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

Pages: 1-

SEPPLES libraries

Name: Anonymous 2012-08-06 15:59

and the eternal quest of MSVC and the linker errors.
May the burdensome weight of 1,000 dongs rain upon you all.

Name: VIPPER 2012-08-06 16:07

Condolences, i got a liker error on mingw once, i think i know how you feel.

Name: Anonymous 2012-08-06 18:43

Oh god I know that feel. Sepples has such an ancient build system, inherited from C.

Name: Anonymous 2012-08-06 20:58

>>3
inherited from C.
Inheritance and code reuse are some of the fundamental aspects of object-oriented programming.

Name: Anonymous 2012-08-06 21:12

maybe check if this little indian or big indian?

Name: Anonymous 2012-08-06 21:57

>>5
Would different sized Indians be different classes?

Name: Anonymous 2012-08-07 0:22

>>6
extends BaseIndian

Name: Anonymous 2012-08-07 5:04


public static BaseIndian createIndianWithSize(int size)

Name: Cudder !MhMRSATORI!fR8duoqGZdD/iE5 2012-08-07 5:17

>>3
Ancient and it works very well. Learn to read C++ encoded names and it's almost trivial to figure out what's wrong.

(I do wish they'd agreed on a standard for that.)

Name: Anonymous 2012-08-07 6:19

>>9
Meanwhile, Common Lisp has an extremely flexible package system which doesn't force static binding upon you.

Name: Anonymous 2012-08-07 9:52

>>10
One day a novice Common Lisp programmer came to the Lisp Master and asked for an advice regarding the extremely flexible package system he was writing. His problem was that while he quickly implemented the basics, then he proceeded to add more and more features allowing for all kinds of flexibility but that just multiplied the possibilities for even more flexibility, with no end in sight.

The Lisp Master inquired where the novice was developing his extremely flexible package system, opened its source in EMACS, and said: "You can't achieve flexibility by adding structure, and every line of code adds structure", with which he promptly C-x h C-k the entire source.

"A blank page you are looking at is the ultimate flexible package manager" he told the horrified novice, who then was enlightened. This is the extremely flexible package manager that CL uses since then, and this is also the approach that CL users learned to apply to all kinds of extremely flexible programs (except fibs and facs) that they don't write all the time.

Name: Anonymous 2012-08-07 12:09

>>10
Common Lisp has an extremely flexible package system
Sorry, I was too busy laughing at you.

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