OT: on writing code

2008-01-28 Thread Mark Wieder
Eric Raymond's talking about Perl vs Python here, but the point's valid (if you're reading the article online, just ignore the comments) "Also, I found I was spending more and more time wrestling with artifacts of the language rather than my application problems. And, most damning of all, the r

Re: OT: on writing code

2008-01-29 Thread Mikey
I would LOVE to see elegant LISP. There's a reason why we nickname it "Lots of Idiotic Stupid Parenthesis". I tried for a long time to write LISP that could actually be read, but it was difficult. Then there's the line about C++ being a "Write-Only" language.

Re: OT: on writing code

2008-01-29 Thread Mikey
xTalk IS very nice. I don't like some of the things RR has done, but it is still much easier to teach someone than many other languages. Yes, I too capital-L LOVE JavaScript as well. ___ use-revolution mailing list use-revolution@lists.runrev.com Please

Re: OT: on writing code

2008-01-29 Thread Andre Garzia
Mikey, http://www.paulgraham.com/onlisptext.html There are copies available in PDF, TXT and others... I'm using the paper version. Lisp can be very elegant if you keep your functions small... Also emacs+slime can do lots of tricks for making it pretty when being displayed. Still, it is difficul

Re: OT: on writing code

2008-01-29 Thread Andre Garzia
Mark, can we say that is impossible to write elegant perl now since perl always look bad... On a side reference, I've been reading both "On lisp" and "Thinking Forth", very nice books with very nice and elegant code. Andre On 1/28/08, Mark Wieder <[EMAIL PROTECTED]> wrote: > Eric Raymond's talk

Re: OT: on writing code

2008-01-29 Thread Luis
Leo Brodie's book has been given the open treatment and is available for free online. Cheers, Luis. On 29 Jan 2008, at 13:28, Andre Garzia wrote: Mark, can we say that is impossible to write elegant perl now since perl always look bad... On a side reference, I've been reading both "On li

Re: OT: on writing code

2008-01-29 Thread Luis
And of course, here is the link: http://thinking-forth.sourceforge.net Cheers, Luis. On 29 Jan 2008, at 15:05, Luis wrote: Leo Brodie's book has been given the open treatment and is available for free online. Cheers, Luis. On 29 Jan 2008, at 13:28, Andre Garzia wrote: Mark, can we s

Re: OT: on writing code

2008-01-29 Thread Thierry
this thread made me think of this. Mmmm, still Eric Raymond :-) "Show me your code and conceal your data structures, and I shall continue to be mystified. Show me your data structures, and I won't usually need your code; it'll be obvious." (the quote is an Eric Raymond (1997) paraphrase of

Re: OT: on writing code

2008-01-29 Thread Mark Wieder
Luis- Thanks - I wasn't aware that this had been released as open-source. I got a nice email from Leo a while back thanking me for web-publishing a reference to his books. -- Mark Wieder [EMAIL PROTECTED] ___ use-revolution mailing list use-revo

Re: OT: on writing code

2008-01-29 Thread Mark Wieder
Andre- Urk. I really didn't want to make this a discussion about perl. Posting the article link was more about thinking about xtalk as a language in the broader definition and in the context of KISS-style coding. -- Mark Wieder [EMAIL PROTECTED]

Re: OT: on writing code

2008-01-29 Thread Luis
Hiya, No problem, thank you. I still dabble in Forth, when the mention came up in the list I had to post the link. Cheers. Luis. On 29 Jan 2008, at 17:09, Mark Wieder wrote: Luis- Thanks - I wasn't aware that this had been released as open-source. I got a nice email from Leo a while ba

Re: OT: on writing code

2008-01-29 Thread Graham Samuel
On Tue, 29 Jan 2008 12:29:06 -0200, "Andre Garzia" <[EMAIL PROTECTED]> wrote: Mikey, http://www.paulgraham.com/onlisptext.html There are copies available in PDF, TXT and others... I'm using the paper version. Lisp can be very elegant if you keep your functions small... Also emacs+slime can

Re: OT: on writing code

2008-01-29 Thread Mikey
Continuing this thread, I'm working on some Java teaching tools, and no matter how I try I just cannot help people get their heads wrapped around int myVar = ++someOtherVar Great. It's short. However since you have three things going on in the same line, it is nearly impossible to absorb it. __

Re: OT: on writing code

2008-01-29 Thread Mark Wieder
Mikey- > int myVar = ++someOtherVar To be fair about this, there's really no reason to start off by placing this all in one line just because you can: int myVar; ++someOtherVar; // or someOtherVar = someOtherVar + 1; myVar = someOtherVar; does the same thing and is (somewhat) easier for newbie

Re: OT: on writing code

2008-01-29 Thread Andre Garzia
Now, just imagine that I am a CS student in a "very easy to be accepted" university here... imagine that most of the students never coded before, actually, their concept of coding is from Hollywood hacker movies now, imagine these guys having to deal pointer arithmetics using Turbo C circa 199

Re: OT: on writing code

2008-01-29 Thread J. Landman Gay
Mark Smith wrote: Well, while we're on the subject of dense code: this is apparently legal C: for(;P("\n"),R--;P("|"))for(e=C;e--;P("_ "+(*u++/8)%2))P("| "+(*u/4)%2); (from the spoof that went round about C and Unix being a hoax). This is identical to what my parrot produces when I allow her t

Re: OT: on writing code

2008-01-29 Thread Mark Smith
Well, while we're on the subject of dense code: this is apparently legal C: for(;P("\n"),R--;P("|"))for(e=C;e--;P("_ "+(*u++/8)%2))P("| "+(*u/4)%2); (from the spoof that went round about C and Unix being a hoax). and this bit of perl is extraordinary: http://99-bottles-of-beer.net/language-pe

Re: OT: on writing code

2008-01-29 Thread Mark Wieder
Mark- This is by far my favorite piece of obfuscated C code: http://www0.us.ioccc.org/1990/westley.c -- Mark Wieder [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe

Re: OT: on writing code

2008-01-30 Thread Mikey
> > int myVar = ++someOtherVar > > To be fair about this, there's really no reason to start off by placing > this > all in one line just because you can: > Believe it or not, that example comes out of the Java tutorials (using different field names to protect the innocent). -- On the first day,

Re: OT: on writing code

2008-01-30 Thread Mick Collins
]> Subject: Re: OT: on writing code To: How to use Revolution Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Mark Smith wrote: Well, while we're on the subject of dense code: this is apparently legal C: for(;P("\n"),R--;P(&quo