A simpler example is the pretty printer in clojure contrib. This has
three component files that make up the common namespace and they are
just loaded in:
(ns clojure.contrib.pprint
(:use clojure.contrib.pprint.utilities)
(:import [clojure.contrib.pprint PrettyWriter]))
(load "pprint/pprint_b
billh04, have a look at the compojure project
(http://github.com/weavejester/compojure/tree/master).
In that James uses an "immigrate" function which may be useful to you.
Also the structure used is a good example of a reasonably large, quite
complex project.
Hth, Adrian.
On Fri, Apr 24, 2009 at
Hi,
Please note that a convention (but it's really just one convention)
could also be to name file for partB : place_partB.clj (or even
place_part_b.clj since in clojure camel case notation is not the
preferred way to write things, hyphens and lower cases are -> but
hyphens must be replaces by u
I don't think I explained my need clearly.
I try to rephrase it. Suppose I have a source file named place.clj in
a directory named whale/achi/model like the following:
place.clj
(ns whale.achi.model.place)
partA
partB
==
What I want to do is to keep the same namesp
billh04 wrote:
> Right now I have the two files "whale.achi.model.place.clj" and
> "whale.achi.model.placeEvaluation.clj" that make up one name space
> "whale.achi.model.place".
> The first file is the "root" of the namespace.
I think you're confused with how Clojure looks for packages in the
fi
I came across the term "root lib" when I googled on how to have one
lib with source in multiple files. But, it appears that this was just
discussion. I couldn't find the information I wanted on the main
clojure page.
Right now I have the two files "whale.achi.
