If defvar was
[doc-string? name init?]
It would obviate defunbound
(defvar "A set of current TCP connections"
connections #{})
And the backward compatible form could still be supported if necessary
[name init? doc-string?]
Regards,
Tim.
--~--~-~--~~~---~--~~
You
On 14/08/2009 19:53, Jarkko Oranen wrote:
>
> I'm not sure whether defonce is useful enough that it should be moved
> to core, so I'll abstain.
>
>
I use defonce and defonce- quite a lot.
I'm all for inclusion of c.c.def in core.
Sacha
--~--~-~--~~~---~--~---
Docs for cutting edge Clojure are on the way. Rich said he was going
to think about the approach he wanted to take and we'll get it up and
running when he gets back from vacation.
Hang tight,
Tom
On Aug 14, 10:21 am, Sean Devlin wrote:
> As long as the documentation doesn't disappear between t
I'm in favour.
Though, I think that a "def-" would be redundant if the defvar macros
are promoted. Perhaps it would be sensible to keep def as a the
underlying special form and just move in defvar, defvar- and
defmacro-.
I'm not sure whether defonce is useful enough that it should be moved
to co
As long as the documentation doesn't disappear between the time the
library is removed from contrib and the appropriate version (1.1, 1.2)
of Clojure is released.
Not-so-subtle hint:
http://groups.google.com/group/clojure/browse_thread/thread/8f191d3a9620977
Sean
On Aug 14, 12:52 pm, Daniel Lyo
On Aug 14, 2009, at 10:10 AM, Chas Emerick wrote:
>
> Seeing that some contrib libs have been promoted into the main clojure
> project, I'd like to suggest that the same be done for
> clojure.contrib.def (or, the majority of it). We use it nearly
> everywhere, and I suspect many others do as we
Seeing that some contrib libs have been promoted into the main clojure
project, I'd like to suggest that the same be done for
clojure.contrib.def (or, the majority of it). We use it nearly
everywhere, and I suspect many others do as well.
As a slight caveat, I'm not sure that the defalias,
