I for one think it sounds like a great idea. The ability to still have strings has value as well though (silly example, any string with a space in it). Lah lah.
But yeah.. the symbol vs string thing, especially in lists of things, definately is a 'bump in the road' for anyone getting going with jess. I'd like to see, if people can provide, pro vs con examples with actual small patterns/situations.. would make the conversation more illustrated. I'll see what I can dig up. Roger On 3/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi Folks, > > As so many newbies learn, painfully, unquoted symbols and > double-quoted Strings are two different data types in Jess. Pattern > matching treats them as distinct, and this is particularaly difficult > when you're dealing with Strings that come in as properties of Java > objects. We've had to explain this many times on this list, and I've > explained it many times in private email as well. > > So my question to you all is: does this make any sense? Jess behaves > this way only because long ago, acting like CLIPS was a priority. I'm > not sure that keeping this behavior makes any sense anymore. > > Let's say that Jess 7, for the purposes of pattern matching, > considered "Foo" and Foo to be equal. Is there anyone reading this who > has code that would break as a result? It would certainly help a lot > of people if this change were made. Let's hear what you think. > > > --------------------------------------------------------- > Ernest Friedman-Hill > Advanced Software Research Phone: (925) 294-2154 > Sandia National Labs FAX: (925) 294-2234 > PO Box 969, MS 9012 [EMAIL PROTECTED] > Livermore, CA 94550 http://herzberg.ca.sandia.gov > > -------------------------------------------------------------------- > To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' > in the BODY of a message to [EMAIL PROTECTED], NOT to the list > (use your own address!) List problems? Notify [EMAIL PROTECTED]
