Make library work on both client and server sides

Replace the two-step compile/match process with a single
compile-and-match one to avoid issues with server-client representation
incompatibility.  Use the browser regex engine on the client side.

1 files changed, 42 insertions, 0 deletions

diff --git a/src/regex__FFI.js b/src/regex__FFI.js
new file mode 100644
index 0000000..fcb8927
--- /dev/null
+++ b/src/regex__FFI.js
@@ -0,0 +1,42 @@
+// Copyright © 2015 Benjamin Barenblat
+//
+// Licensed under the Apache License, Version 2.0 (the "License"); you may not
+// use this file except in compliance with the License.  You may obtain a copy
+// of the License at
+//
+//     http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+// WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  See the
+// License for the specific language governing permissions and limitations under
+// the License.
+
+var UrWeb = { Regex: {
+
+succeeded: function(match) {
+  return !!match;
+},
+
+nSubexpressionMatches: function(match) {
+  return match.length - 1;
+},
+
+subexpressionMatch: function(match, n) {
+  if (match.length - 1 <= n) {
+    er("regex: match does not exist");
+  }
+  return match[n + 1];
+},
+
+doMatch: function(needle_string, haystack) {
+  var needle;
+  try {
+    needle = new RegExp(needle_string);
+  } catch (e) {
+    er("regex: compilation failed");
+  }
+  return haystack.match(needle);
+},
+
+}};  // UrWeb.Regex