JESS: Who cares about chars?

Currently, Jess maps Java char values onto Jess Strings; i.e., the result of (call foo charAt 0) is f. I'm starting to think that this is the wrong mapping -- a Jess integer would make more sense (i.e., 102.) Does anybody have an opinion, one way or the other?

RE: JESS: Who cares about chars?

Title: RE: JESS: Who cares about chars? -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Why have it return an int instead of a char like the java.lang.String.charAt() method does? Also, with a method name like charAt, I would intuitively expect a char type to be returned. - -Bryan

Re: JESS: Who cares about chars?

Well, Jess has its own LISP-like type system, following the one from CLIPS. Jess has one type that Java doesn't (symbols) and doesn't make many of the distinctions that Java does. For the most part this doesn't matter; in a very high-level language, you're generally not worrying about data types.

Re: JESS: Who cares about chars?

Just my two cents: Returning int or char is far better than returning String. Object creation time is one of our big problems in Java. Right? SDG jco [EMAIL PROTECTED] wrote: Well, Jess has its own LISP-like type system, following the one from CLIPS. Jess has one type that Java doesn't