Hi,

I also plan to use sjacket in the near future, so I'm looking forward to 
hear about your experiences with it.

BTW Codeq does code analysis too, http://blog.datomic.com/2012/10/codeq.html

JW

On Monday, December 31, 2012 1:08:58 PM UTC+1, Malcolm Sparks wrote:
>
> Jozef, 
>
> sjacket turns out to be better suited for my purposes because tools.reader 
> (blind) is just a reader and throws away formatting and comments, since I 
> want the source intact Christophe's parser (within sjacket) is ideal, so 
> thanks for the tip!
>
> Ideally a future tools.reader would have the option to retain formatting 
> and comments, even those these are 'not so homoiconic'. I see the 
> capability to use Clojure to manage (and manipulate) Clojure source code to 
> be a huge advantage when Clojure source bases become larger - the problems 
> you run into with large Clojure code-bases are different from Java ones, 
> but there all the same.
>
> Regards,
>
> Malcolm
>
> On Thursday, December 27, 2012 10:45:26 PM UTC, Jozef Wagner wrote:
>>
>> This may also help https://github.com/cgrand/sjacket
>>
>> On Thursday, December 27, 2012 9:32:10 PM UTC+1, Malcolm Sparks wrote:
>>>
>>> Thanks David, that was just the library I was looking for :)
>>> On 27 Dec 2012 20:22, "David Nolen" <dnolen...@gmail.com> wrote:
>>>
>>>> https://github.com/Bronsa/blind
>>>>
>>>> This library is on its way to becoming a part of contrib as tools.reader
>>>>
>>>>  David
>>>>
>>>>
>>>> On Thu, Dec 27, 2012 at 3:17 PM, Malcolm Sparks <mal...@congreve.com>wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I need to parse Clojure code for purposes of code-insights, web 
>>>>> presentation with hyperlinks between symbols, potential re-factoring, 
>>>>> dead 
>>>>> namespace illumination, visualization and inspection of increasingly 
>>>>> large 
>>>>> Clojure code-bases, code-style and compliance violation monitoring, that 
>>>>> kind of thing... 
>>>>>
>>>>> Most of the functionality I need is locked away in private methods of 
>>>>> clojure.lang.LispReader, so I wondered if there was something else I 
>>>>> could 
>>>>> re-use.
>>>>>
>>>>> I've recently come across https://github.com/cosmin/clojure-in-clojure 
>>>>> and 
>>>>> I remember Christophe Grand's presentation at EuroClojure last May which 
>>>>> promised some source-manipulation library that could be shared across 
>>>>> projects.
>>>>>
>>>>> Can anyone help point me to the current 'state of the art' with 
>>>>> respect to parsing Clojure itself? Is there such a thing?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Malcolm
>>>>>  
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Clojure" group.
>>>>> To post to this group, send email to clo...@googlegroups.com
>>>>> Note that posts from new members are moderated - please be patient 
>>>>> with your first post.
>>>>> To unsubscribe from this group, send email to
>>>>> clojure+u...@googlegroups.com
>>>>> For more options, visit this group at
>>>>> http://groups.google.com/group/clojure?hl=en
>>>>
>>>>
>>>>  -- 
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Clojure" group.
>>>> To post to this group, send email to clo...@googlegroups.com
>>>> Note that posts from new members are moderated - please be patient with 
>>>> your first post.
>>>> To unsubscribe from this group, send email to
>>>> clojure+u...@googlegroups.com
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/clojure?hl=en
>>>
>>>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Reply via email to