Hans Hubner's BKNR framework for CL explores this in a very
interesting way - while relying on CLOS meta-object protocol the ideas
could prob. be extended to Clojure. With some ABCL interaction this
would make CL -> Clojure || Clojure -> CL interop possible at the JVM
level with persistence...
So
> This seems like a reasonable restriction for Clojure too.
Third rule. Macros break the rules. Don't place arbitrary
restrictions on rule breaking :P
s_P
On Dec 19, 2:05 pm, Stuart Halloway wrote:
> According to Paul Graham's On Lisp, macroexpanders should be purely
> functional, and you sh
> I have a strong dislike for the concept of TIMTOWTDI (There is more
> than one way to do it .
This should be a guiding design goal for any core lisp devel. Get the
core right and TIMTOWTDI is a `side effect' of good design rather than
the inverse.
s_P
On Dec 19, 7:36 am, "Mark Volkmann" wrote
> I would propose, that the files are hosted where ever
> they are hosted now with suitable labels with which
> Clojure version they work. This works out of the box
> with the least amount of trouble.
>
> Meikel
In contrast to the monolithic GG Code repo or C*AN or git/hg/bzr.*hubs
I find that th
Some thoughts on really stupid things that have tripped me up:
- How do I exit Clojure - srsly
C-c
- Whatsa JVM - does this mean Clojure is really just Java with parens?
- Whatsa Classpath?
this answer presents the *ALL* important opportunity to mention that
*nix uses `:' to separate paths wher
> This is why flatten's behavior was considered a bug. In Clojure, an
> empty sequence is equivalent to nil, not to '(nil).
This does not comport with the various differences enumerated @
http://clojure.org/lisps
Perhaps they need to be changed. RH care to weigh in on this?
which says:
"() is n
For FAQ style plain text I like having the RHS comments moved below
the S-Expression as I can C-n down the file and do C-x C-e evaluation
to REPL as I go.
Once the RHS ;;;Comments are below the S-Expressions I find i like
having a symbol to indicate the eval =>
I took the liberty of re-formattin
whoops, chopped of the end of that last message - forgot the nasake-no
ichigeki
user> (seq? '(nil))
==|]==>true
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To post to this group, send email
he only
source of codified design rationale.
> Sorry, Mon Key, but I have to agree with Randall here.
Is it not ok to have free will around here? :)
While it may be reasonable to expect (flatten nil) to return nil, as
written and as documented in the working context - flatten doesn't
appea
Clojure needs a FAQ - a plain old school vanilla FAQ.
Clojure.org is useful;
The wiki is useful;
The gg Group is useful;
The /# clojure is useful;
(doc some-fn) is useful;
(show some-fn) is useful;
None of these are a FAQ.
None accomplish what a FAQ accomplishes.
Lots of people look for a FAQ
> > > I would expect (flatten nil) => nil
Why?
=> nil
nil is not a sequence - your expectation is that Clojure flatten and
return `nothing'... which *would* be a bug
Not a bug. Implementation deficiency/wrong expectations/
preconceptions/mis-application of earlier idiom to new platform.
@ http
> user=> (flatten nil)
> (nil)
Not a bug.
flatten returns a sequence - in this case a sequence containing 'nil.
How else would you flatten on nil?
In the former cases the flatten returns the seq - nil
Can Clojure return an empty sequence otherwise?
(def x ())
(first x)
=> nil
(def y x)
y
=> n
> user=> (flatten nil)
> (nil)
Not a bug.
flatten returns a sequence - in this case a sequence containing 'nil.
How else would you flatten on nil?
In the former cases the flatten returns the seq - nil
Can Clojure return an empty sequence otherwise?
(def x ())
(first x)
=> nil
(def y x)
y
=> n
> Clojure does not allow for programmer-defined
> reader macros (unlike other lisps).
I know this has been touched upon last Spring - and Stu Halloway refs
at least one discussion of this in his book.
>From a practical standpoint I am beginning to understand more why the
choice was made to not s
> Clojure does not allow for programmer-defined
> reader macros (unlike other lisps).
I know this has been touched upon last Spring - and Stu Halloway refs
at least one discussion of this in his book.
>From a practical standpoint I am beginning to understand more why the
choice was made to not s
cool. was wondering if this was possible the other day myself :)
Good to know RH & crew have accounted for this possibility already.
s_P
On Dec 11, 10:08 pm, Chouser wrote:
> On Thu, Dec 11, 2008 at 7:49 PM, Robert Koberg wrote:
>
> > Hi,
>
> > Would it be desirable to further define keywords
The PCL -> Clojure blog helped turn me on to Clojure... She's a
valuable asset.
Glad to see she hasn't been left wearing a red dress out in the rain.
You must be swamped with the book deadlines.
Thank You for making the time to continue sharing and updating the pcl
-> clojure code.
On Dec 9, 10:
> I've been converting some projects to Clojure for the past few months...
> but thinking about them enough to express the issue clearly has so far
> always resulting in my solving them easily.
This is GREAT to hear. I personally place considerable measure on
accounts such as yours because they o
Nice blog entry :)
My setup tends to mirror yours esp. as I've culled most of it from
your blog over the years...
Most of my startup scripts are modified versions of those you've
shared elsewhere.
I don't segment it out quite so much as it makes for transporting
directory trees difficult, and my
n-also-do-two x y)))
On Dec 4, 5:41 pm, Meikel Brandmeyer <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Am 04.12.2008 um 18:30 schrieb Mon Key:
>
> > It looks like I was getting turned around by the implicit do (and by
> > my preconceptions coming from other Lisps where the docstr
#x27;t :)
> def foo
> "evaluted and lost"
> "return value"
> end
So, it would have been safer to assume Ruby like behaviour :)
On Dec 4, 2:22 am, Meikel Brandmeyer <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On 4 Dez., 07:53, Mon Key <[EMAIL PROTECTED]> wrote
===
(defn my-test
[]
"misplaced documentation string for my-test"
(= my-test my-test))
(defn my-test
[]
""
(= my-test my-test))
On Dec 4, 1:23 am, "Stephen C. Gilardi" <[EMAIL PROTECTED]> wrote:
> On Dec 4, 2
ram
;;; ===
user> my-test
#
;;; ===
Here again the only difference is the placement of the (doc)string -
which can't be discerned visually.
On Dec 4, 12:57 am, Mon Key <[EMAIL PROTECTED]> wrote:
> I'm sure I'm missing something
>
;; evaluating doc of my-test defn with doc string *before* param
;;; ===
user> (doc my-test)
-
user/my-test
([])
appropriately placed documentation string for my-test
nil
;;; ===========
On Dec 3, 11:58 pm, "Stephen C. Gilardi&qu
I apologize if this has been brought up before... But, where does the
doc
string on the `my-test' defn below reside.
In case one evaluating (doc my-test returns the doc string. In case
two (doc evaluates the string as nil).
Is this value interned with the symbol and if so where and how do I
ac
ure'
and/or `exit-clojure' available as a tab-complete in addition to
leaving open the shorter tokens `quit' and `exit' for future potential
uses or User Code makes sense.
s_P
On Dec 2, 2:07 pm, "Cosmin Stejerean" <[EMAIL PROTECTED]> wrote:
> On Sun, Nov 30,
;; you can evaluate:
(defn myfirst [x] (mysecond x))
;; then bind that to:
(defn mysecond [x] (+ x 1))
user> (myfirst 1)
=> 2
Which winds up being more better once you let go of the CL assumptions
about ns :)
I'm finding that part difficult as well.
On Dec 1, 10:47 pm, "[EMAIL PROTECTED]" <[EMAI
;; you can evaluate:
(defn myfirst [x] (mysecond x))
;; then bind that to:
(defn mysecond [x] (+ x 1))
user> (myfirst 1)
=> 2
Which winds up being more better once you let go of the CL assumptions
about ns :)
I'm finding that part difficult as well.
On Dec 1, 10:47 pm, "[EMAIL PROTECTED]" <[EMAI
Maybe (quit-clojure) instead of (quit)? This would save vanilla `quit'
just in case it's needed later/elsewhere.
Might also be nice to have (exit-clojure). Ditto saving vanilla `exit'
for other purposes
When first configuring Clojure on both linux box and windows from the
command line (e.g. pre-s
29 matches
Mail list logo
