km-qa Google Group

Does anyone know if there is a Java JVM version of lisp that can run KM?

2008-08-07T23:48:56Z

[16:11] <dmiles_afk> in ABCL has anyone experienced problems that multiple
values get returned due to they are buffered from inner calls?
[16:13] <dmiles_afk> i am trying to figure out why i am having issues with
[link]
Does anyone know if there is a Java JVM version of lisp that can run KM?

interaction w/protege?

2008-07-22T06:56:41Z

Has anyone tried having KM interact with [link] ?

Re: pairp function

2008-07-10T16:56:39Z

Oops you're right! My two versions have different functionality for
dotted pairs (should return NIL, not error). Thanks for the updated
version of your pairp, that works as intended now, it will be in the
next KM release in the next day or so.

Best wishes! Pete

Re: pairp function

2008-07-09T06:46:45Z

No, the original function (which is also the one currently used in SBCL) generates an error:
KM 4 > (defun pairp (list)(and (listp list) (eq (length list) 2)))
pairp
KM 5 > (pairp '(1 . 2))
Error: In a call to length of (1 . 2), tail 2 is not a LIST.
This should be what you want:
;;; return T if thing is 2 elements proper list

Re: pairp function

2008-07-08T16:05:06Z

Actually, Francis, the behavior isn't quite correct - unlike the
original, it (undesirably) generates an error (rather than NIL) when
the argument is a dotted pair:

CL-USER(4): (pairp '(a . b))
Error: Attempt to take the cdr of B which is not listp.
[condition type: TYPE-ERROR]

So I'll leave the original in place for now. Pete

Re: pairp function

2008-07-08T16:01:56Z

Thanks, Francis, it will be in the next KM release. Best wishes! Pete

pairp function

2008-06-26T15:41:11Z

Hello,
Here is a version of the optimized pairp function that should work for any Lisp (I also get a bug with LispWorks 5.1):
- the declaration is now correct.
- the function works exactly like the original one.
;;; thing: should be anything but a dotted list
(defun pairp (thing)
(declare (optimize (speed 3) (safety 0)))

internship opportunity

2008-05-01T17:38:04Z

Hello All,

I’m looking for a graduate student, preferably at the PhD level, who
would be interested in conducting research/development on "situation
sensemaking" for a period of 6 month at a well know software company
in Palo Alto, California. The starting date can range from mid May to
mid June this Summer. Please respond privately to cys...@gmail.com

KM 2.2.0 - rationalizing behavior on errors

2008-05-01T02:44:12Z

I've just uploaded KM 2.2.0. This rationalizes the parameters
controlling KM's behavior on error into a single variable, as
described below from the RELEASE-NOTES.txt:

2.2.0 - **NOTE**
The parameters controlling behavior on errors have been
rationalized
to a single parameter. *abort-on-error-report*, *error-report-

Re: KM patch

2008-02-26T04:58:31Z

Reini -

Thanks for the info. I've reinstated the old (space-inefficient)
version of
xmlify in KM 2.1.19 as you suggested, so macrolet is no longer needed
and KM
should again be compatible with clisp.

Thanks! Pete

Re: KM patch

2008-02-06T10:17:23Z

Even Francis Leboutte's improved xmlify macrolet doesn't work for
clisp, it still creates
a cyclic structure.
I fixed it by enabling the old space-intensive version for clisp and
forget about Carl Shapiro's version.

$ ln -s km-2-1-18-packaged.lisp km.lisp
$ clisp -c km.lisp
WARNING in IMMEDIATE-CLASSES in lines 6663..6734 :

Re: KM patch

2008-02-04T14:43:55Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
see also
[link]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - [link]
iD8DBQFHpySrPp1Qsf2qnMcRAjABAJ 9xFXjrrpFqFI95GrO7/LkrKF62gACf VaEg

Re: spurious blanks in km-2-1-11.lisp

2008-01-15T20:44:15Z

Oops, you're right! Fixed in KM 2.1.12 on the Web site (no other
changes). Thanks for pointing this out! Pete

On Jan 15, 8:58 am, Raphael Van Dyck <raphael.vand...@labage.be>
wrote:

spurious blanks in km-2-1-11.lisp

2008-01-15T16:58:26Z

Hello.
I just wanted to tell that there are some spurious blanks in the files km-2-1-11.lisp and
km-2-1-11-packaged.lisp.
Those blanks are located at the top of the included sadl.lisp file:
;;; FILE: sadl.lisp
^^^^^^^^^^^^^^^
spurious blanks
Because of those blanks the extraction of the file sadl.lisp fails:

Must Read

2007-06-11T11:07:44Z

New article has been added on the Measurement and Analysis section as
defined by the CMMI standards. Worth Reading!!!
[link]