[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

No Subject

Carl --

I think that the (* intersect) will turn out to be generally useful.
It provides an explicit way to represent what is going on, and so just
for documentation purposes it is very useful.  And, as you process
an intersection, there may be several ways to "get stuck", e.g.
	(* intersect (* prefix "2000-01")
		     (* range date "1999" "2005"))
might an intermediate term you end up with, and you reduction engine
might not know how to deal with it.  So, with (* intersect) available
as a primitive, you can just leave this piece in this form, and process
the other parts.
Also, I like the logical completeness of having both (* set) and (* intersect).

From: Carl Ellison <cme@cybercash.com>
Subject: Re: *-forms
Cc: spki@c2.net, blampson@microsoft.com

At 06:43 AM 4/5/97 EST, Ron Rivest wrote:
>	-- we introduce a new *-form:
>		(* intersect s1 s2 ... sk)

This is reasonably clean but I'm not sure there's an advantage to it over 
deciding in the 5-tuple engine not to do cross products (as per my previous 

|Carl M. Ellison  cme@cybercash.com   http://www.clark.net/pub/cme |
|CyberCash, Inc.                      http://www.cybercash.com/    |
|207 Grindall Street   PGP 2.6.2: 61E2DE7FCB9D7984E9C8048BA63221A2 |
|Baltimore MD 21230-4103  T:(410) 727-4288  F:(410)727-4293        |