diff options
| author | Rob Austein <sra@hactrn.net> | 2006-07-23 05:30:54 +0000 |
|---|---|---|
| committer | Rob Austein <sra@hactrn.net> | 2006-07-23 05:30:54 +0000 |
| commit | c2d20a529de6eb0024967747f76593fd630167e3 (patch) | |
| tree | e1629a6632b752e6edbdf85bc0c438622b8ac7b6 | |
| parent | 4855ab2bd85f876da027613e5cc435eedc95ea1e (diff) | |
Merge function.
svn path=/openssl/README; revision=52
| -rw-r--r-- | openssl/README | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/openssl/README b/openssl/README index ec85d3cf..b9a5fb11 100644 --- a/openssl/README +++ b/openssl/README @@ -341,3 +341,15 @@ Problem is, this requires data not available in a sk_sort() handler. So I think we're stuck with the temporary stack approach. No, we can use a closure. + + + +addr_canonize() code is not right yet, mostly because merging prefixes +and ranges is tricky. Logic that checks whether they need to be +merged is probably ok, it's the code that does the merge that's whacked. + +Perhaps what we need is a function that takes two prefix-or-ranges +(which the caller asserts should be merged), and generates the prefix +or range that starts with the first one and ends with the second. +Would probably be easier than what the code does now. Worry about +optimizing this later, if it matters, get it right first. |