Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

name clashes and *in* problem #1

Open
rpergl opened this issue Oct 2, 2010 · 1 comment
Open

name clashes and *in* problem #1

rpergl opened this issue Oct 2, 2010 · 1 comment

Comments

@rpergl
Copy link

rpergl commented Oct 2, 2010

Hi, I have some names clashes when using lambdebug and the worse: it has some problems with missing in. Please help. Thanks!

lein repl
WARNING: flatten already refers to: #'clojure.core/flatten in namespace: lambdebug.utils, being replaced by: #'clojure.contrib.seq-utils/flatten
WARNING: spit already refers to: #'clojure.core/spit in namespace: lambdebug, being replaced by: #'clojure.contrib.duck-streams/spit
WARNING: spit already refers to: #'clojure.core/spit in namespace: lambdebug.core, being replaced by: #'clojure.contrib.duck-streams/spit
finParse.core=> (debug '(run))
Warning: No source for #'clojure.core/in

@adamschmideg
Copy link
Owner

The WARNINGs are given by Clojure 1.2.0. It was fixed in SHA: 102f5c9 but not released to clojars yet. You can download the current source or wait until my next release, soonish.

The Warning about #'clojure.core/in is given by lambdebug, but it tells you only that lambdebug won't be able to debug this function (well, it's not a function, so this shouldn't even give a warning). Note however that debugging an interactive application may not work because of the way lambdebug works, first running the whole program, then pretending it gets executed step-by-step. If you provide the source of your run function, I could explore this issue further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants