From: Ramza Brown
Subject: Lisp for java developers
Date: 
Message-ID: <ZOudne0szYr4-GPfRVn-tQ@comcast.com>
I kind of write this little blog that basically is about me learning 
lisp code and how a java developer might get interested in it.  This 
latest one has pictures.

http://www.jroller.com/page/berlinbrown?entry=writing_quick_lisp_tools_and

Please ignore lispness of the code...(sigh)

-- 
Ramza from Atlanta
http://www.newspiritcompany.com
From: A.L.
Subject: Re: Lisp for java developers
Date: 
Message-ID: <3p9tf19irthjmdi2e4dhr7uas1l15gmvfc@4ax.com>
On Sat, 13 Aug 2005 17:25:51 -0400, Ramza Brown
<············@gmail.com> wrote:

>I kind of write this little blog that basically is about me learning 
>lisp code and how a java developer might get interested in it.  

Why Java developer might be interested in it?...

A.L.
From: Marco Antoniotti
Subject: Re: Lisp for java developers
Date: 
Message-ID: <tI2Me.29$DJ5.68416@typhoon.nyu.edu>
A.L. wrote:
> On Sat, 13 Aug 2005 17:25:51 -0400, Ramza Brown
> <············@gmail.com> wrote:
> 
> 
>>I kind of write this little blog that basically is about me learning 
>>lisp code and how a java developer might get interested in it.  
> 
> 
> Why Java developer might be interested in it?...

To be enlightened? :)

Cheers
--
Marco
From: Edi Weitz
Subject: Re: Lisp for java developers
Date: 
Message-ID: <u7jepebon.fsf@agharta.de>
On Sat, 13 Aug 2005 17:25:51 -0400, Ramza Brown <············@gmail.com> wrote:

> I kind of write this little blog that basically is about me learning
> lisp code and how a java developer might get interested in it.  This
> latest one has pictures.
>
> http://www.jroller.com/page/berlinbrown?entry=writing_quick_lisp_tools_and
>
> Please ignore lispness of the code...(sigh)

I haven't really looked at the code itself but it's definetly a
disservice to Lisp if you're publishing unindented code like in your
WALK-LIGHT function.  This'll only confirm the misconception of most
non-Lispers that Lisp is hard to read because of "all the
parentheses."  Let Emacs indent your code correctly or do it yourself
and only after that post it in your blog.

Thanks,
Edi.

-- 

Lisp is not dead, it just smells funny.

Real email: (replace (subseq ·········@agharta.de" 5) "edi")
From: Ramza Brown
Subject: Re: Lisp for java developers
Date: 
Message-ID: <JMCdnfIWqIip6mPfRVn-pg@comcast.com>
Edi Weitz wrote:
> On Sat, 13 Aug 2005 17:25:51 -0400, Ramza Brown <············@gmail.com> wrote:
> 
> 
>>I kind of write this little blog that basically is about me learning
>>lisp code and how a java developer might get interested in it.  This
>>latest one has pictures.
>>
>>http://www.jroller.com/page/berlinbrown?entry=writing_quick_lisp_tools_and
>>
>>Please ignore lispness of the code...(sigh)
> 
> 
> I haven't really looked at the code itself but it's definetly a
> disservice to Lisp if you're publishing unindented code like in your
> WALK-LIGHT function.  This'll only confirm the misconception of most
> non-Lispers that Lisp is hard to read because of "all the
> parentheses."  Let Emacs indent your code correctly or do it yourself
> and only after that post it in your blog.
> 
> Thanks,
> Edi.
> 

I did publish the indented code, the jroller service messes up pre and 
syntax highlighting.  I have pictures and the full source highlighted.

http://www.newspiritcompany.com/imgs/simple_lisp_code.jpg
http://www.newspiritcompany.com/src/walk-files.lisp.html


-- 
Ramza from Atlanta
http://www.newspiritcompany.com
From: Marco Antoniotti
Subject: Re: Lisp for java developers
Date: 
Message-ID: <dK2Me.30$DJ5.68416@typhoon.nyu.edu>
Hi

you need to fix a number of things in your pages.

E.g.  what you call a "block comment" is actually a "documentation 
string" which you can access with the DOCUMENTATION function.
Block comments in CL (properly nesting) are delimited by #| and |#

Cheers
--
Marco




Ramza Brown wrote:
> Edi Weitz wrote:
> 
>> On Sat, 13 Aug 2005 17:25:51 -0400, Ramza Brown 
>> <············@gmail.com> wrote:
>>
>>
>>> I kind of write this little blog that basically is about me learning
>>> lisp code and how a java developer might get interested in it.  This
>>> latest one has pictures.
>>>
>>> http://www.jroller.com/page/berlinbrown?entry=writing_quick_lisp_tools_and 
>>>
>>>
>>> Please ignore lispness of the code...(sigh)
>>
>>
>>
>> I haven't really looked at the code itself but it's definetly a
>> disservice to Lisp if you're publishing unindented code like in your
>> WALK-LIGHT function.  This'll only confirm the misconception of most
>> non-Lispers that Lisp is hard to read because of "all the
>> parentheses."  Let Emacs indent your code correctly or do it yourself
>> and only after that post it in your blog.
>>
>> Thanks,
>> Edi.
>>
> 
> I did publish the indented code, the jroller service messes up pre and 
> syntax highlighting.  I have pictures and the full source highlighted.
> 
> http://www.newspiritcompany.com/imgs/simple_lisp_code.jpg
> http://www.newspiritcompany.com/src/walk-files.lisp.html
> 
>
comp.lang.lisp / 2005 / aug