Stencil is spec compliant (the tests actually run against the spec) while
this implementation is not. A major goal behind stencil is to be totally
spec compliant and as fast as possible. However, implementing the slow
parts of the spec is important too.
On Wednesday, July 11, 2012 6:28:23 PM
But the real issue is the stacktrace one. In this case, the bug could
have been found by static analysis. But in general, it can not.
I experienced this same issue and tracked it down to a bug in goog, at
least in my case.
In my case, I was making a JSON request to the server. When the
response
Yes, you are right. Stencil did a very good job.
I only implement a subset. Test
codehttps://github.com/shenfeng/mustache.clj/blob/master/test/me/shenfeng/mustache_test.clj
.
Set Delimiter and lambdas and Dotted Names are not implemented.
The algorithm of this implementation is borrowed from
Try to add in project.clj:
:jvm-opts [-Djava.library.path=native/linux])
where it will point to folder with OS specific libraries.
Regards,
Sanel
On Monday, July 9, 2012 4:26:05 AM UTC+2, Karl Smeltzer wrote:
Is anybody willing and able to walk me through getting a simple project
Eric in San Diego:
That's why I'm hoping there is some way I can compare and contrast the actual
inputs that get fed into the app.
At least post your exception message.
MK
mich...@defprotocol.org
signature.asc
Description: Message signed with OpenPGP using GPGMail
Thank you for the report. I have a fix for the LRU/LU caches on my box
and will have it out in the next day or so. The core.memoize changes
will follow soon after.
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to
Hi, folks.
Just a quick newbie question.
One can create lazy sequences by wrapping each sequence element inside a
'lazy-seq' macro while constructing the sequence. Usually it's done with
recursion. But what if I need a tail recursive construction of the sequence
(using recur) accumulating
It's very application specific, but it's Object 'test' does not have a
field named 'test1' c:/path/to/importTest, suggesting that it's not
inferring the value of an 'I' parameter which should indicate a directory
within which to search for a file called 'test' which included some trivial
