Hi Kashyap,
> While I see the big pieces based on the description given in doc/app.html,
> I need some help understanding the Pilog queries.
>
> I think I can make progress if I could figure out how to run the pilog
> queries in the sample app on the REPL. For example, how can I run the pilog
>
Good bye Mark Probert :-(
You are now unsubscribed
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Thank you Alex,
I get the following when I run the (?) - for which I defined a function XX.
I do see that I get back 1 record when *CuSuNm is "Oaks" and 3 records when
*CuSuNm is "". However, I don't see the actual values - except for @Nm.
While at it, could you also explain the @/@@ convention?
On Mon, Oct 21, 2019 at 06:16:41AM -0700, C K Kashyap wrote:
> Thank you Alex,
> I get the following when I run the (?) - for which I defined a function XX.
Good.
> I do see that I get back 1 record when *CuSuNm is "Oaks" and 3 records when
> *CuSuNm is "". However, I don't see the actual values
Finally - its good to see the values :) ... I used (show @@).
I see, so @@ is just a "variable" introduced in the select function - i got
a little confused by (@@) - I thought it was a function call - but looks
like select takes the argument unevaluated :) (love the (vi 'select) )
I noticed that
Thanks Alex,
So, would you suggest that I familiarize myself with prolog before
venturing deeper into app development in picolisp?
I think it will be helpful for me if I could get an english translation of
this?
(?
@Nr (and *CuSuNr (cons @ T))
@Nm *CuSuNm
@Tel *CuSuTel
@Plz
On Mon, Oct 21, 2019 at 07:12:32AM -0700, C K Kashyap wrote:
> Finally - its good to see the values :) ... I used (show @@).
> I see, so @@ is just a "variable" introduced in the select function - i got
> a little confused by (@@) - I thought it was a function call - but looks
> like select takes