looking for MOP documentation

[Holger Krekel]

OK, I disagree with you, too

Nah, that's almost impossible because I have carefully interspersed
the above sentence with "probably" and "more obviously"

http://www.elwoodcorp.com/alu/mop/contents.html

Uuh, it's all LISP based, i see. Maybe i still give it a try. Anyone
willing to give a pythonic crash-course in LISP in - say -
10 x 5-line paragraphs?

looks like being a version of AMOP online, you know that book I
brought with me to one of the pypy sprints (actually, it may have
been the Gothenbourg sprint). I can bring it to the next sprint I
come to, if you like.

sounds good and like more fun than funding papers.

cheers,

holger

 

[Alex Martelli]

Michael Hudson wrote:
...

Fair enough. I can see your point of view, I just don't (completely)
agree with it You could have something with similar syntax,
keywords, etc to Python but semantics like C, and it would still be
horrible (IMHO).

Tried pyrex? It comes reasonably close to the "something" you
describe, and it ain't all that horrible (IMHO).


Alex

 

[Michael Hudson]

Michael Hudson wrote:
...

Tried pyrex? It comes reasonably close to the "something" you
describe, and it ain't all that horrible (IMHO).

I'm not sure pyrex is all that close to what I meant. I meant
something like this:

include "stdio.h"

def main(int argc, char** argv):
char* s = "world"
if argc == 2:
s = argv[1]
printf("Hello %s", s)

OK, so maybe it's a little nicer than regular punctuation-soup C but I
really do think it's the object model of Python plus having high-level
types *right there* in the language that makes Python so useful (as
opposed to the syntax which just makes it *pleasant*).

Cheers,
mwh

 

[Michael Hudson]

Nah, that's almost impossible because I have carefully interspersed
the above sentence with "probably" and "more obviously"

OK, you're right in what you say -- the syntax probably does make more
of an obvious impact. I'll carry on believing that the powerful data
structures are more important, but that hardly contradicts your
paragraph.

Uuh, it's all LISP based, i see.

Well, CLOS (== Common Lisp Object System). Difficulties in
understanding are likely to come as much from not grokking CLOS as not
grokking Lisp.

Maybe i still give it a try. Anyone willing to give a pythonic
crash-course in LISP in - say - 10 x 5-line paragraphs?

Not right now, sorry...

sounds good and like more fun than funding papers.

Actually, the URL isn't the text of the book, but is similar
material...

Cheers,
mwh