I'll write some preliminary documentation. However, since the actual API hasn't been settled on yet, it will probably have to change.
As for the name, I don't have much of a preference, other than noting that I've never seen the abbreviation "rex" being used in any context. The common ones tend to be "re", "regex" and "regexp", so on of them would probably be logical. But, as I said, I don't care much either way. Regards, Elias On 4 Oct 2017 19:13, "Juergen Sauermann" <juergen.sauerm...@t-online.de> wrote: > Hi Elias, > > maybe you want to write a brief description of *⎕RE* for *doc/apl.texi* ? > And should we maybe call it *⎕REX*? > > Best Regards, > Jürgen > > > On 10/04/2017 12:30 PM, Elias Mårtenson wrote: > > Thanks. > > The version I sent to you still uses "B" as the code go produce > ⊂-compatible output. You might want to change that in Quad_RE.cc if you > want. > > Regards, > Elias > > On 4 October 2017 at 18:06, Juergen Sauermann < > juergen.sauerm...@t-online.de> wrote: > >> Hi Elias, >> >> yes, I will do so. May take a few days though. >> >> Best Regards, >> /// Jürgen >> >> >> On 10/04/2017 07:43 AM, Elias Mårtenson wrote: >> >> Here's the diffs for the current version of regexp support. It's probably >> stable enough to use for real so that we can get some feedback on it. >> >> Do you want to merge this? >> >> Regards, >> Elias >> >> >> > >
