Alexander Burger schrieb:
OK, I understand.
The language is not useful or usable, and the Community (I count 70
members in this list) is silent.
Oh oh ...
Alex, your conclusion is not necessary true. If most are silent that has
not to mean, they conclude with Henrik. At least me, if I do
Alexander Burger wrote:
Hi Cle,
Hi Alex,
(setq *Signals NIL)
(de _storeElement (@Queue)
(curry (@Queue) (Attributes . SubExprs)
(queue '@Queue Attributes)
NIL
)
)
(setq strml:Signal (_storeElement *Signals
Alexander Burger wrote:
Hi Cle,
Hi Alex,
(...)
The most languages
try the hell to avoid such ugly things like a SIGSEGV or SIGBUS ;-)
PicoLisp doesn't want to do that. After all, these are error messages,
resulting from hardware runtime tests, optimal in terms of efficiency
compatibility clauses.
Another idea could be auxpilog.l ...
But as you mention it where in sync with other extensions, where in the
picoLisp sources are other files following that scheme i.e.
extwhatever.l. It seems to me, that extpilog.l would be the first
one, wouldn't it?
Ciao,
cle.
--
UNSUBSCRIBE
Alexander Burger wrote:
Hi Cle,
Hi Alex,
(...)
Yeah! I like this a lot better :-D That prove you again being the guru
and me the disciple :-)
Not at all! I must say your discovery of using 'fill' here is ingenious.
A nice coincidence of Lisp pattern variables versus Pilog
Alexander Burger wrote:
Hi Cle,
Hi Alex,
The usage of 'unify' is interesting, however. I had found it, but did
not understand, how to use it from the manual. It seems, it is only
usable in Lisp statements of Pilog clauses. Otherwise, I got SIGSEGV
regulary :-/
Yeah, it tries
(collect) and (aux) for
more utility functions that will let you access the DB without using
Pilog.
But in the end, I *want* to use Pilog, I explain in the later mail. :-)
(...)
Thank you for your non-ending effort to answer my noob questions :-)
Ciao,
cle.
--
UNSUBSCRIBE: mailto:picol
Alexander Burger wrote:
Hi Cle,
Hi Alex,
let me first correct some errors:
(pool test)
This is a funny one. As the value of 'test' is a function
definition, you get a rather strange database file ;-)
Ahhh ... this was a copy/paste error from the console into the mail. My
DB file
-lisp/
I had already a fly-over over your site, it is really nice done! I will
look at it again, though. But I think, I will have no problem with
Pilog, but more with the database thingy :-)
(...)
Ciao,
cle.
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
Alexander Burger wrote:
Hi Cle,
Hi Alex,
(...)
If 'new' is called this way, it will not create database objects
but
... :-O But ... but ... but ... URGHS! :-( I had looked especially
into the x.db file and found my keys 1, 11 and 111 there.
So I thought
Right. I never tried
Alexander Burger wrote:
Hi Cle,
Nice idea! Now I reformulated my Pilog rules for usage with database
like this:
(be graph:walk (@Begin @Way)
(@E db 'id '+DB:Edge (- @Begin))
(@To get (- @E) 'tgt)
(graph:walk @To (@Begin) @Way)
)
(be graph:walk (@Node @Way
Alexander Burger wrote:
Hi Cle,
Hi Alex,
back from shopping outside, I read your explanations. Let me thank you.
Although I have read the reference manual several times (and have it
open while I am coding) I did oversee 'push' and 'queue' totally :-( But
I know about 'inc' but for my learning
Alexander Burger wrote:
Hi Cle,
Hi Alex,
(dm foos () (mapcar cdr (val (: Foos))) )
..
Howevery only if the receiver is the class. If I use an instance
as receiver, it would not work! I would like to code the method the
way, that the method will work regardless if the receiver is a
class
) to the documentation,
how would I have to submit them? In which format?
Ciao,
cle.
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
feedback (or error notes)
welcome!
At least it worked under MacOS/X 10.6 (Intel) and 10.5 (PPC). :-)
But I would suppose to document this proposal also in the Reference
Manual under Naming Conventions.
Cheers,
- Alex
Ciao,
cle.
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject
not reach the first
1000 solutions before I lost my patience ;-)
Or is there any way to improve the performance of the DB? For instance
by only matching exactly in the db query for a certain edge?
Thanks and Ciao,
cle.
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
for the type of every instance held
in the association list *2b* will answer +Foo correctly. But sending a
'show' to every instance (*2c*) will repsond with Bad message.
So please enlight me, where is my stumble block? What did I wrong?
Thanks and ciao,
cle.
--
UNSUBSCRIBE: mailto:picol...@software-lab.de
Alexander Burger wrote:
Hi Cle,
Hi Alex,
(...)
But please note that there is one difference (or bug?) that Jon
Kleiser found out about two years ago, and which I could not
resolve:
Anonymous variables ('@' in Pilog, '_' in Prolog) may not work as
expected, when there is more than
Alexander Burger wrote:
Hi Cle,
Hi Alex,
(...)
Yes, the work-around is easy: Just use variables '@1', '@2' instead of
'@'. It is just rather inelegant, and may produce unwanted output :-(
jupp, so I will have a look at this, if this problem will bite me one
day :-)
The next
as ever! Thank you. With that explanation I eventually got also
my 'assertz' got right! Previously it did not assert my desired clause.
But you explanation above let me realize, that there too, a extra pair
of parentheses were lacking ... :-)
Cheers, - Alex
Ciao,
Cle.
--
UNSUBSCRIBE
Alexander Burger wrote:
Hi Cle,
Hi Alex,
although not intended so, it seems I mutate the picoLisp mailing list
into a Pilog mailing list ;-)
Which is a good thing. This way we produce at last some Pilog
documentation ;-)
nice you see it that way :-)
(be attributes
Alexander Burger wrote:
Hi Cle,
Hi Alexander,
(...)
I see. The unit tests are a little special. As they need a
well-defined environment to operate correctly, they have to be
started in a certain way. It is written as a comment in the 5th line
of lib/test.l:
# $(/bin/pwd)/p lib
in advance ...
Ciao,
Cle.
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
Alexander Burger wrote:
Hi Cle,
Hello Alex,
(...)
Thank you for the list of rules, this will be very helpful :-)
(be member (@X (@X . @)))
(be member (@X (@ . @Y)) (member @X @Y))
(be append (NIL @X @X))
(be append ((@A . @X) @Y (@A . @Z)) (append @X @Y @Z))
Wow, these are very
)
(or (t1 @N) (t2 @N)))
Now calling (? (aT @N)) is running like the Prolog version and therefore
as I expected. But running (? (bT @N)) will return NIL at once.
So I would like to ask, if 'or' works as intended or if there is a bug?
Thanks in advance and ciao,
Cle.
--
UNSUBSCRIBE: mailto:picol
Alexander Burger wrote:
Hi Cle,
Hello Alexander,
Alexander Burger wrote:
Hi Cli,
Oops, sorry ;-)
Macht nischt! :-D
(...)
Now I'm wondering why you extended the setting of the 'Home' global
in init(), to fall back to the current working directory if the first
file argument
Alexander Burger wrote:
Hi Cle,
Hi Alexander,
unfortunately, we see problems on Mac OS since quite some time.
You'll see that if you search in the archive of this mailing list
(http://www.mail-archive.com/picolisp@software-lab.de).
I had already seen this, but those problems dealt
an idea what the reason for this could be? Any hint,
what I can do to spot the problem?
Thanks in advance for any idea you may have ...
Regards,
Cle.
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
Hello cle cle-picol...@qiao.in-berlin.de :-)
You are now subscribed
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
29 matches
Mail list logo
