On Fri, Aug 5, 2011 at 10:21 AM, Meikel Brandmeyer (kotarak)
wrote:
> Hi,
>
> Am Freitag, 5. August 2011 15:56:28 UTC+2 schrieb faenvie:
>
>> so in your case after initial load of the knowledge-base there are no
>> changes
>> that need to be persisted, right ?
>>
>
> Exactly. It's not a running s
Hi,
Am Freitag, 5. August 2011 15:56:28 UTC+2 schrieb faenvie:
>
> so in your case after initial load of the knowledge-base there are no
> changes
> that need to be persisted, right ?
>
Exactly. It's not a running server process or the like. Just a simple small
tool. The input data are create
hi meikel
so in your case after initial load of the knowledge-base there are no
changes
that need to be persisted, right ?
following stefan tilkovs book i want to do a simple RESTful
order-management (exercise only) and think of using core.logic
for query-logic.
persisting changes to rdbms seems
On Fri, Aug 5, 2011 at 8:29 AM, Meikel Brandmeyer (kotarak)
wrote:
> Hi,
>
> Am Freitag, 5. August 2011 14:06:58 UTC+2 schrieb David Nolen:
>
>
> > Nope there's a not in the source to switch to refs and transactions.
>
> Woops. Indeed. I missed the comment.
>
>
> >> And a last question: Is this s
Hi,
Am Freitag, 5. August 2011 14:06:58 UTC+2 schrieb David Nolen:
> Nope there's a not in the source to switch to refs and transactions.
Woops. Indeed. I missed the comment.
>> And a last question: Is this something like (or developed to or help
>> to move) contrib.datalog?
>
> As far as I can
On Fri, Aug 5, 2011 at 7:46 AM, faenvie wrote:
> hi david,
>
> thanks for the sample ...
>
> as you have asked for questions, i take the chance for asking
> a question that's in my mind for some times now:
>
> are there concepts for how to combine core.logic (minikanren) with
> (database backed)
On Fri, Aug 5, 2011 at 2:19 AM, Meikel Brandmeyer (kotarak)
wrote:
> I agree. Clojure does a lot to separate such concerns. facts modifies two
> atoms. Is this save in all cases?
>
Nope there's a not in the source to switch to refs and transactions.
> Another superficial question: Should facts
On Thu, Aug 4, 2011 at 7:18 PM, Laurent PETIT wrote:
>
> What kind of "strict control over state mutation" stories can we expect
> when using core.logic ?
> I mean, in the above example, I see no explicit use of refs, and I see
> somewhat "unmanaged" state change with the introduction of the new c
hi david,
thanks for the sample ...
as you have asked for questions, i take the chance for asking
a question that's in my mind for some times now:
are there concepts for how to combine core.logic (minikanren) with
(database backed) long term persistence ?
my reasing: there must be, because pro
Hi,
Am Freitag, 5. August 2011 01:18:45 UTC+2 schrieb lpetit:
> What kind of "strict control over state mutation" stories can we expect
> when using core.logic ?
> I mean, in the above example, I see no explicit use of refs, and I see
> somewhat "unmanaged" state change with the introduction
Hello David,
2011/8/5 David Nolen
> On Wed, Aug 3, 2011 at 5:26 AM, Rickard Lindberg wrote:
>
>> Hi,
>>
>> I am interested in Clojures approach to managing state and its use of
>> immutable
>> values. I believe immutable values will make the life of programmers
>> easier and
>> I'm trying to fig
On Wed, Aug 3, 2011 at 5:26 AM, Rickard Lindberg wrote:
> Hi,
>
> I am interested in Clojures approach to managing state and its use of
> immutable
> values. I believe immutable values will make the life of programmers easier
> and
> I'm trying to figure out how I can simplify my OO code by using
Hi,
2011/8/3 Rickard Lindberg
> Hi,
>
> I am interested in Clojures approach to managing state and its use of
> immutable
> values. I believe immutable values will make the life of programmers easier
> and
> I'm trying to figure out how I can simplify my OO code by using more
> immutable
> value
I like to have the datastructure as one big mutable structure. It's not
optimal in many cases, but it is simple.
In this case you could have something like:
(def NoteDb
(atom
[{:text "a note" :category :misc}
{:text "note 2" :category :misc}
{:text "blabla" :category :important}]))
(defn
Hi,
I am interested in Clojures approach to managing state and its use of immutable
values. I believe immutable values will make the life of programmers easier and
I'm trying to figure out how I can simplify my OO code by using more immutable
values.
In particular, I am wondering how I can model
15 matches
Mail list logo
