<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">It is trivial (in my mind) to
programmatically generate a regular expression given the *, ?, and
n's provided in the proposed to-call list. Maintaining two
separate fields is error prone, especially when they are
expressing a single thing. And for mere mortal consumption (yes,
people DO look up ToCalls by hand) and ease of human understanding
and maintenance, I'd propose keeping the single declaration and
let programmers massage it as necessary.<br>
<br>
IMHO, *?n is easier to parse for the purposes of constructing a
regular expression than trying to convert whatever expression
dialect is published to whatever expression dialect is required by
any given information consumer. Personally I'm most recently
using lua (<a href="http://www.lua.org/pil/20.1.html">http://www.lua.org/pil/20.1.html</a>)
which has it's own pattern specification which I wouldn't dream of
forcing on other software authors (see below).<br>
<br>
But I can certainly programmatically convert APWM?? to
^APWM(%w%w)$ for my internal use.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
Win32<br>
<br>
PS. Here's the match characters for lua (along with ^ and $ for
anchors) in case anyone is interested:<br>
<br>
<table style="font-family: 'New Century Schoolbook', 'Century
Schoolbook', 'Century Schoolbook L', serif; letter-spacing:
normal; orphans: auto; text-indent: 0px; text-transform: none;
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);" align="center" border="1">
<tbody>
<tr>
<td><code>.</code></td>
<td>all characters</td>
</tr>
<tr>
<td><code>%a</code></td>
<td>letters</td>
</tr>
<tr>
<td><code>%c</code></td>
<td>control characters</td>
</tr>
<tr>
<td><code>%d</code></td>
<td>digits</td>
</tr>
<tr>
<td><code>%l</code></td>
<td>lower case letters</td>
</tr>
<tr>
<td><code>%p</code></td>
<td>punctuation characters</td>
</tr>
<tr>
<td><code>%s</code></td>
<td>space characters</td>
</tr>
<tr>
<td><code>%u</code></td>
<td>upper case letters</td>
</tr>
<tr>
<td><code>%w</code></td>
<td>alphanumeric characters</td>
</tr>
<tr>
<td><code>%x</code></td>
<td>hexadecimal digits</td>
</tr>
<tr>
<td><code>%z</code></td>
<td>the character with representation 0</td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
On 10/24/2013 5:28 AM, Georg Lukas wrote:<br>
</div>
<blockquote cite="mid:20131024092858.GA7873@ovgu.de" type="cite">
<pre wrap="">* Heikki Hannikainen <a class="moz-txt-link-rfc2396E" href="mailto:hessu@hes.iki.fi"><hessu@hes.iki.fi></a> [2013-10-24 08:43]:
</pre>
<blockquote type="cite">
<pre wrap="">I would prefer taking a regexp library (pcre) and just throw the
tocall spec found in the database file at it, instead of writing my
own converters, since writing custom converters takes time and effort
and may introduce bugs. String matching is sooooo a solved problem
already. :)
</pre>
</blockquote>
<pre wrap="">
+1 on that. I would really like to have an easy way (regular
expressions) to a) determine the client info block and b) extract the
version number.
My proposal would be to leave the tocall as-is, and add another
(slightly redundant) "regex" field that allows to match for the tocall
and to extract the version number, e.g. "^APWM(\d\d)$" (I hope I did not
botch the syntax now, but the point is just to make the intent clear).
Does YAML require any type of escaping for such strings?
73 de Georg DO1GL
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<br>
</body>
</html>