/jp/ - Otaku Culture

[Satorin Komeiji !!2iqYZrZ3IOK No.]

Satori time?

[Anonymous No.]

No Satori until you've read you're SICP!

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Anonymous No.]

[Tohno ♥ ‮ufiaw iam si iganiM ‪‪‪‬ !!UhnG3iuGcmC No.]

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Anonymous No.]

We are about to study the idea of a computational process. Computational processes are abstract beings that inhabit computers. As they evolve, processes manipulate other abstract things called data. The evolution of a process is directed by a pattern of rules called a program. People create programs to direct processes. In effect, we conjure the spirits of the computer with our spells.

A computational process is indeed much like a sorcerer's idea of a spirit. It cannot be seen or touched. It is not composed of matter at all. However, it is very real. It can perform intellectual work. It can answer questions. It can affect the world by disbursing money at a bank or by controlling a robot arm in a factory. The programs we use to conjure processes are like a sorcerer's spells. They are carefully composed from symbolic expressions in arcane and esoteric programming languages that prescribe the tasks we want our processes to perform.

A computational process, in a correctly working computer, executes programs precisely and accurately. Thus, like the sorcerer's apprentice, novice programmers must learn to understand and to anticipate the consequences of their conjuring. Even small errors (usually called bugs or glitches) in programs can have complex and unanticipated consequences.

[Satorin Komeiji !!2iqYZrZ3IOK No.]

The Satori love the better~

[Anonymous No.]

Fortunately, learning to program is considerably less dangerous than learning sorcery, because the spirits we deal with are conveniently contained in a secure way. Real-world programming, however, requires care, expertise, and wisdom. A small bug in a computer-aided design program, for example, can lead to the catastrophic collapse of an airplane or a dam or the self-destruction of an industrial robot.

Master software engineers have the ability to organize programs so that they can be reasonably sure that the resulting processes will perform the tasks intended. They can visualize the behavior of their systems in advance. They know how to structure programs so that unanticipated problems do not lead to catastrophic consequences, and when problems do arise, they can debug their programs. Well-designed computational systems, like well-designed automobiles or nuclear reactors, are designed in a modular manner, so that the parts can be constructed, replaced, and debugged separately.

Programming in Lisp

We need an appropriate language for describing processes, and we will use for this purpose the programming language Lisp. Just as our everyday thoughts are usually expressed in our natural language (such as English, French, or Japanese), and descriptions of quantitative phenomena are expressed with mathematical notations, our procedural thoughts will be expressed in Lisp. Lisp was invented in the late 1950s as a formalism for reasoning about the use of certain kinds of logical expressions, called recursion equations, as a model for computation. The language was conceived by John McCarthy and is based on his paper ``Recursive Functions of Symbolic Expressions and Their Computation by Machine'' (McCarthy 1960).

[Anonymous No.]

Despite its inception as a mathematical formalism, Lisp is a practical programming language. A Lisp interpreter is a machine that carries out processes described in the Lisp language. The first Lisp interpreter was implemented by McCarthy with the help of colleagues and students in the Artificial Intelligence Group of the MIT Research Laboratory of Electronics and in the MIT Computation Center.1 Lisp, whose name is an acronym for LISt Processing, was designed to provide symbol-manipulating capabilities for attacking programming problems such as the symbolic differentiation and integration of algebraic expressions. It included for this purpose new data objects known as atoms and lists, which most strikingly set it apart from all other languages of the period.

Lisp was not the product of a concerted design effort. Instead, it evolved informally in an experimental manner in response to users' needs and to pragmatic implementation considerations. Lisp's informal evolution has continued through the years, and the community of Lisp users has traditionally resisted attempts to promulgate any ``official'' definition of the language. This evolution, together with the flexibility and elegance of the initial conception, has enabled Lisp, which is the second oldest language in widespread use today (only Fortran is older), to continually adapt to encompass the most modern ideas about program design. Thus, Lisp is by now a family of dialects, which, while sharing most of the original features, may differ from one another in significant ways. The dialect of Lisp used in this book is called Scheme.2

[Satorin Komeiji !!2iqYZrZ3IOK No.]

Best sister~

[Satorin Komeiji !!2iqYZrZ3IOK No.]

ah, i love spam~

[Anonymous No.]

Because of its experimental character and its emphasis on symbol manipulation, Lisp was at first very inefficient for numerical computations, at least in comparison with Fortran. Over the years, however, Lisp compilers have been developed that translate programs into machine code that can perform numerical computations reasonably efficiently. And for special applications, Lisp has been used with great effectiveness.3 Although Lisp has not yet overcome its old reputation as hopelessly inefficient, Lisp is now used in many applications where efficiency is not the central concern. For example, Lisp has become a language of choice for operating-system shell languages and for extension languages for editors and computer-aided design systems.

If Lisp is not a mainstream language, why are we using it as the framework for our discussion of programming? Because the language possesses unique features that make it an excellent medium for studying important programming constructs and data structures and for relating them to the linguistic features that support them. The most significant of these features is the fact that Lisp descriptions of processes, called procedures, can themselves be represented and manipulated as Lisp data. The importance of this is that there are powerful program-design techniques that rely on the ability to blur the traditional distinction between ``passive'' data and ``active'' processes. As we shall discover, Lisp's flexibility in handling procedures as data makes it one of the most convenient languages in existence for exploring these techniques. The ability to represent procedures as data also makes Lisp an excellent language for writing programs that must manipulate other programs as data, such as the interpreters and compilers that support computer languages. Above and beyond these considerations, programming in Lisp is great fun.

[Anonymous No.]

1.1 The Elements of Programming

A powerful programming language is more than just a means for instructing a computer to perform tasks. The language also serves as a framework within which we organize our ideas about processes. Thus, when we describe a language, we should pay particular attention to the means that the language provides for combining simple ideas to form more complex ideas. Every powerful language has three mechanisms for accomplishing this:

* primitive expressions, which represent the simplest entities the language is concerned with,

* means of combination, by which compound elements are built from simpler ones, and

* means of abstraction, by which compound elements can be named and manipulated as units.

In programming, we deal with two kinds of elements: procedures and data. (Later we will discover that they are really not so distinct.) Informally, data is ``stuff'' that we want to manipulate, and procedures are descriptions of the rules for manipulating the data. Thus, any powerful programming language should be able to describe primitive data and primitive procedures and should have methods for combining and abstracting procedures and data.

In this chapter we will deal only with simple numerical data so that we can focus on the rules for building procedures.4 In later chapters we will see that these same rules allow us to build procedures to manipulate compound data as well.

[Anonymous No.]

1.1.1 Expressions

One easy way to get started at programming is to examine some typical interactions with an interpreter for the Scheme dialect of Lisp. Imagine that you are sitting at a computer terminal. You type an expression, and the interpreter responds by displaying the result of its evaluating that expression.

One kind of primitive expression you might type is a number. (More precisely, the expression that you type consists of the numerals that represent the number in base 10.) If you present Lisp with a number

486

the interpreter will respond by printing5

486

Expressions representing numbers may be combined with an expression representing a primitive procedure (such as + or *) to form a compound expression that represents the application of the procedure to those numbers. For example:

(+ 137 349)
486
(- 1000 334)
666
(* 5 99)
495
(/ 10 5)
2
(+ 2.7 10)
12.7

[Anonymous No.]

I can't no one has posted this yet.

Let me explain in detail what it would be like to cum inside of Satori. After a day of browing /jp/, you'd hear the door close and a small sigh before hearing the most angelic voice announcing its return. Of course it would be Satori, the love of your life, arriving home from school. You call out to her that you're in your room (where you always are, you don't do anything with your life anyway), and you hear the sweet pitter-patter of her foot steps as she skips over to your door. You hear it squeak and turn around to see her poking her head inside with an unsure look on her face. Once your eyes meet though, she smiles and that in turn makes you smile. You offer her a spot on your bed right next to you, and she happily walks over and sits down happily next to you, putting her head infront of your face, looking at the computer screen. "This again? I knew you were into this kind of thing but I never imagined it would come to being this common", she exclaims in a bored sounding voice. As she turns around and your eyes meet once again, she can tell you're feeling aroused by being near her, smelling her, hearing her sweet voice. She knows you absolutely adore her. "It's very nice of you to think that way about me, but I don't know if I'm ready for something like that", she exclaims.

[Anonymous No.]

>>4720815
Those last few words. “Something like that”, you think to yourself. Suddenly you imagine what she was talking about. You imagine yourself on top of Satori's naked body, grinding your hips into hers, hearing her make a small grunt everytime your penis drives into her wetness, and one of the sweetest sighs you've ever heard from someone when you pull it out. “Stop that”. It’s Satori. Satori is beside of you and you’re both sitting in your bed. You're start looking at Satori in the face, and she's staring back directly at you, with a look of great concentration on her face. After a short silence, she quickly mutters the phrase, "How lewd". You can see her face is very red, her brow is creased and she's almost making a scowling face at you, as if disgusted by your thoughts. While her back is turned to you and she’s starting to walk away, one of the most wicked ideas in your entire life floods your mind. You will cum inside of Satori right now. You grab her by her hips and pull her onto your lap. Surprisingly, she doesn’t resist. “What are you do-,“ was all she could get out before your mouth covers hers. She lets out a moan. You know she wasn’t being serious when she had that look on her face. Maybe she was looking for an excuse to get away from you to relieve her frustration. You’ve been living together for a few years now, anyway. It would have been very frustrating for her to wait for a timid and weak person like yourself to make the first move, lest she look like a slut. She knows how much you adore pure girls. Pure, little girls just like herself. She let you enjoy her for so many years, and now it was finally time to show her how thankful you are for that.

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Kilga M. Aya~n !2BklmILFiE No.]

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Anonymous No.]

Damn it, that wasn't spam, whichever idiot called the mods.
That was SICP!

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Kilga M. Aya~n !2BklmILFiE No.]

[Kilga M. Aya~n !2BklmILFiE No.]

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Satorin Komeiji !!2iqYZrZ3IOK No.]

Isn't /jp/ such a great place?

[Quagsire !BALDCFdFzA No.]

[Kilga M. Aya~n !2BklmILFiE No.]

[Anonymous No.]

Oh boy! Reposts from 2 days ago, I was on the edge of my seat waiting for this.

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Kilga M. Aya~n !2BklmILFiE No.]

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Kilga M. Aya~n !2BklmILFiE No.]

[Anonymous No.]

thx 4 danbooru thread op i came on cat and cat reported for ban evasion

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Kilga M. Aya~n !2BklmILFiE No.]

[Kilga M. Aya~n !2BklmILFiE No.]

[Satorin Komeiji !!2iqYZrZ3IOK No.]

>>4720852
I'm glad you enjoy it~

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Satorin Komeiji !!2iqYZrZ3IOK No.]

Sadly, I have work soon so this dump won't go very far...sorry.

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Satorin Komeiji !!2iqYZrZ3IOK No.]

[Anonymous No.]

>>4720746
WHAT THE SHIT IS WRONG WITH HER FOOT
O GOD
THAT LOOKS LIKE IT HURTS

[Anonymous No.]

For anyone that missed this last satori thread

[Satorin Komeiji !!2iqYZrZ3IOK No.]

Alright last one, see you guys tomorrow...any suggestions on a thread?