Thanks for everyone's feedback. Sound like the code, in general, is
basically right. Probably some of the issues that I'm having with the
code comes from simply not being terribly familiar with reading
clojure code.
--
You received this message because you are subscribed to the Google
Groups "Clo
On Jan 18, 2011, at 8:54 PM, Lee Spector wrote:
> Also BTW I saw no clear performance improvement (relative to the overall
> runtime of my system); some numbers on that are also below.
A perf differential will be seen if slot access is a significant portion of the
algorithms in question. IIRC
On Jan 18, 2011, at 7:21 PM, Chas Emerick wrote:
> You might find my minor sugar for defining records whose slots have default
> values:
>
> http://cemerick.com/2010/08/02/defrecord-slot-defaults/
Nice -- I do think it'd be good for something like this to be built in.
> Also worth noting is th
On Jan 18, 2011, at 5:38 PM, Lee Spector wrote:
> If I recall correctly the lack of nil defaults was indeed one of the things
> that I didn't like about records (I think this was leading to exceptions in
> my code until I patched around it), and it's even possible that the IFn thing
> meant th
On Jan 18, 2011, at 6:01 PM, Alan wrote:
> On Jan 18, 2:38 pm, Lee Spector wrote:
>> On Jan 18, 2011, at 5:03 PM, Alan wrote:
>>
>>> Deprecated doesn't mean "in future this will stop working" - it means
>>> "you shouldn't use this". See
>>> eghttp://dictionary.reference.com/browse/deprecate.
>
On Jan 18, 2:38 pm, Lee Spector wrote:
> On Jan 18, 2011, at 5:03 PM, Alan wrote:
>
> > Deprecated doesn't mean "in future this will stop working" - it means
> > "you shouldn't use this". See
> > eghttp://dictionary.reference.com/browse/deprecate.
>
> None of those definitions appear to address t
On Jan 18, 2011, at 5:03 PM, Alan wrote:
> Deprecated doesn't mean "in future this will stop working" - it means
> "you shouldn't use this". See eg
> http://dictionary.reference.com/browse/deprecate.
None of those definitions appear to address this technical usage, and in my
experience "depreca
On Jan 18, 1:17 pm, Lee Spector wrote:
> On Jan 18, 2011, at 1:02 PM, Ken Wesson wrote:
>
> I haven't looked at the OP's context for this, but I rather like defstruct
> and I want to ask about its status.
>
> I see some mention on the web of it being deprecated in 1.2 (e.g.
> inhttp://stackove
On Jan 18, 2011, at 1:02 PM, Ken Wesson wrote:
> On Tue, Jan 18, 2011 at 12:37 PM, Alan wrote:
>> defstruct is old and I'm pretty sure there's no reason to use it.
>> defrecord is a drop-in replacement though for something simple and not
>> performance-sensitive you might consider just using has
On Jan 18, 2011, at 10:59 AM, Tim Visher wrote:
> I'd love to have the code torn apart a little bit and get some
> suggestions for improvements.
>
> It's located at https://gist.github.com/784744
It took me a few tries to figure out what to-wallpaper-name was doing. Maybe
you should write a he
On Tue, Jan 18, 2011 at 12:37 PM, Alan wrote:
> defstruct is old and I'm pretty sure there's no reason to use it.
> defrecord is a drop-in replacement though for something simple and not
> performance-sensitive you might consider just using hashmaps.
Agree, but in a case like this there's no stro
defstruct is old and I'm pretty sure there's no reason to use it.
defrecord is a drop-in replacement though for something simple and not
performance-sensitive you might consider just using hashmaps.
to-resolution seems like it should be named get-resolution or
resolution-of or something, but the i
On Tue, Jan 18, 2011 at 11:59 AM, Tim Visher wrote:
> Hi Everyone,
>
> I'm attempting to use Clojure to write a Wallpaper Library app. My
> first stab at a small subset of the functionality is done and I can't
> see how to improve it. I'm not particularly happy with it from a
> readability perspec
13 matches
Mail list logo
