On Tuesday, November 8, 2011 8:04:19 AM UTC+2, Sean Corfield wrote:
docstrings?
Yeah, sure, but docstrings aren't linkable. It's interesting that Java,
with all its faults, has an incredible documentation system. Scala has a
problem in this field, too, since the complex typing and tricks
On Tue, Nov 8, 2011 at 3:14 AM, pron ron.press...@gmail.com wrote:
Yeah, sure, but docstrings aren't linkable. It's interesting that Java, with
all its faults, has an incredible documentation system.
Have you looked at autodoc? It's responsible for generating stuff like this:
On Tuesday, November 8, 2011 8:42:13 PM UTC+2, Sean Corfield wrote:
Have you looked at autodoc?
Yes, but it lacks cross-referencing and linking from within the docstrings
themselves (like Javadoc's @See). I would like to suggest tagging in order
to compensate for the lack of Javadoc's
On Tue, Nov 8, 2011 at 4:09 PM, pron ron.press...@gmail.com wrote:
Yes, but it lacks cross-referencing and linking from within the docstrings
themselves (like Javadoc's @See).
You can use :see-also metadata to cause autodoc to generate
cross-references with links... I think it would be pretty
Am 06.11.2011 12:56, schrieb pron:
Hi. I'm new to Clojure, and enjoy using it very much. It's been years
since I learned Scheme back in college, and it's a pleasure going back
to lisp.
I do, however, have a question regarding real-world Clojure use in large
teams. While I clearly understand
I see. So namespaces are helpful here.
What other team practices do you use? E.g. what do you use for effective
documentation? With Java you can easily find all helpful operations that
can be used to manipulate a type. How do you make sure developers find all
relevant functions in Clojure and
I'm new to all this, too. The kinds of teams I've worked on, generally,
favor breaking down a problem into separate processes such that we each get
to work on our own apps which communicate via messaging or http, so I may
not have quite the experience you have with big shared-code libraries
Oops. I somehow it some magic key. Soon as that post makes it through
review I'll rewrite it to something short and useful. Moral of the story
is to not use the web form on Google Groups.
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to
actually, we avoid dynamically typed languages like the plague. i am
taking a peek at clojure because i'm curious.
Am 07.11.2011 11:19, schrieb pron:
I see. So namespaces are helpful here.
What other team practices do you use? E.g. what do you use for effective
documentation? With Java you
On Mon, Nov 7, 2011 at 2:19 AM, pron ron.press...@gmail.com wrote:
What other team practices do you use? E.g. what do you use for effective
documentation?
docstrings?
I understand my questions could be directed at most dynamic languages, and
I'm absolutely not entering the static vs. dynamic
On Mon, Nov 7, 2011 at 10:23 AM, Dennis Haupt d.haup...@googlemail.com wrote:
actually, we avoid dynamically typed languages like the plague.
Why? Genuinely curious...
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. --
On Sun, Nov 6, 2011 at 03:56, pron ron.press...@gmail.com wrote:
Hi. I'm new to Clojure, and enjoy using it very much. It's been years since
I learned Scheme back in college, and it's a pleasure going back to lisp.
I do, however, have a question regarding real-world Clojure use in large
On 6/11/2011 12:56, pron wrote:
E.g., one developer may add a keyword to a map for one purpose, and
another, use the same keyword for a different purpose. With classes,
all data manipulation for a single type is located in one place, so
such clashes can easily be prevented, let alone the fact
On Sun, Nov 6, 2011 at 3:56 AM, pron ron.press...@gmail.com wrote:
I realize there are always tradeoffs, and perhaps the pros outweigh the
cons, but I would like to know how you deal with such problems, that
invariably arise in large-team development.
Why do you think this sort of problem is
14 matches
Mail list logo
