This is my helpler function.

(defn isEqual [a b] (identical? a b))

(defn anotherHelper [a b]

)

See this: https://stackoverflow.com/questions/17971466/java-regex-overlapping-matches, then try: (count (re-seq #"(?=(bb))." "bbbbb"))

Thank you; however, I am trying to do it only using clojure. I am having hard time sub-string part like compare bbbb and bb. make bbbb as bb.

(defn starts-with? [a b] (= (subs a 0 (min (count a) (count b))) b))

and then you can probably do something like that:

(->> (range (count a))
     (map (fn [i] (subs a i)))
     (filter (fn [s] (starts-with? s b)))
     (count))

it would be more efficient to change subs with the end index, and simply use = in filter

using identical is a bad idea, you can have 2 string that are equal but not the same object

(identical? "bb" (subs "bbb" 0 2)) => false (= "bb" (subs "bbb" 0 2)) => true

These are output I expect. (ptnCount "abababa" "aba") returns 3 (ptnCount "bbbb" "bb") returns 4 (ptnCount "Dabde" "dab") returns 0

At the moment, I am thinking to use subs or partitions to get substrings.

partition by length of second string, step 1

I don’t know in particular (because I’m not sure exactly what behavior you’re referring to), but in general, I would say that it’s because a reference in a def is determined at the time of evaluating the form, as opposed to a defn which doesn’t evaluate immediately. It’s effectively a def/`fn` and anything inside the fn won’t be evaluated until the fn gets called.

the terms I'm using might be incorrect. the evaluation of a symbol return its value. the evaluation of the body of the function happens when the function is called (def a (println "hello)) (defn a [] (println "hello"))

ah yeah, good point. the symbol is resolved but it's not evaluated until the enclosing function is executed/evaluated.

This is the behavior I'm talking about:

user=> (defn adder [a] (+ 10 a))
#'user/adder
user=> (def example {:adder adder :adder-var #'adder})
#'user/example
user=> (defn example-fn [b] (adder b))
#'user/example-fn
user=> ((:adder example) 5)
15
user=> ((:adder-var example) 5)
15
user=> (example-fn 5)
15
user=> (defn adder [a] (+ 20 a))
#'user/adder
user=> ((:adder example) 5)
15
user=> ((:adder-var example) 5)
25
user=> (example-fn 5)
25

I suspected that you were referring to this

Yes, it’s a time-of-evaluation issue

cool, thanks y'all

Note that :adder-var is not the function, it’s a reference to the name

so by evaluating it, it has to look up the current binding for the var, rather than whatever value was in the var when the map was created

(I hope that didn’t read like circular reasoning)

Right, it evaluates to the var object, which holds a reference to a function definition (aka java class)

not at all, thanks for the extended explanation

Unrelated to the original question… I really like that the name of a var can be used this way, because it lets me refer to things that are private. e.g. The internal print function is clojure.core/pr-on

user=> (clojure.core/pr-on [1 2 3] *out*)
Syntax error (IllegalStateException) compiling clojure.core/pr-on at (REPL:1:1).
var: #'clojure.core/pr-on is not public

user=> (#'clojure.core/pr-on [1 2 3] *out*)
[1 2 3]nil

Yeah, that's a great feature.

I’m not sure if circumventing the principle of information hiding is what we should be calling a “feature”, but I love that I can 🙂

i like to think of it as a feature. I don't think fully locking access is ideal, as sometimes you need that access, but making it require an additional step keeps everyone honest about what they're doing (compared to, for example, Python that has no privacy at all)

i mean you're using a map but that's not even necessary:

(def x inc)
(def y x)
(y 1) => 2
(def x dec)
(y 1) => 2

Oh yeah, good catch

There's similar problem with spec function instrumentation. It's a tradeoff between (at least) performance and dynamicity / developer friendliness

you should not need to install react-hightlight manually. Do you still get this error with the latest version of re-frame-10x ? They do not depend on react-hightlight anymore, that lib is unmaintained

That seems to have helped! But when I try the latest version (1.5.0) of re-frame-10x, I get a different error. A build failure that starts like this:

------ ERROR -----
 File: jar:file:/home/epidiah/.m2/repository/org/babashka/sci/0.2.8/sci-0.2.8.jar!/sci/impl/namespaces.cljc
failed to require macro-ns "sci.impl.namespaces", it was required by "sci.impl.namespaces"
Error in phase :compile-syntax-check
RuntimeException: No such var: edamame/normalize-opts

are you using lein, deps, or shadow-cljs ? if you're using lein, try lein deps :tree to see if their is a version conflict

and if 2 dependencies depend on edaname try forcing the most recent one

you could probably even try to see if directly adding [borkdude/edamame "1.0.0"] to force a recent version works, but it's still worth it to check what causes the conflcit to document it IMO

Thank you! The tutorial in the book uses lein and shadow-cljs. I did the lein deps :tree trick and it looks like there were 2 dependencies depending on edamame. Adding the latest version of edamame to project.clj seems to have solved that. Now I'm shadow-cljs is telling me I have "Stale Output!" but I think that might be a story for another day. Thank you for talking me through this!

Hi, I'm also still studying that book, Back then when I was facing that problem, I messed around with installing npm install react (edited, i forgot if i use the react-dom too or not, i don't remember it and still can't find the solution website) and react-highlight.js recklessly based on the solution i got on the internet without think twice or upgrading to latest version in project.clj (not recommended of course) , but you know what? voila!, it works haha. The only problem i faced 'till now after i did that was just the dependency conflict since i use the react newest version, but as long as it works, no problem (don't take it seriously haha.) But thank you for addressing this issue, i learned a lot after reading the replies and will do that solutions in the future when i'm want to mastering that book.