discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Peter Bray <pdb_ml@yahoo.com.au>
Cc: discuss@mdocml.bsd.lv
Subject: Re: Solaris 10 regcomp() does not handle simple whatis query
Date: Fri, 3 Apr 2015 14:52:59 +0200	[thread overview]
Message-ID: <20150403125259.GD7421@athene.usta.de> (raw)
In-Reply-To: <551E8148.7070004@yahoo.com.au>

Hi Peter,

Peter Bray wrote on Fri, Apr 03, 2015 at 11:02:16PM +1100:

> I am having trouble viewing the GMAME web archive of the mailing
> list, so please excuse me if this post is a repeat of a known issue.

Duplicate reports are better than missing ones, so unless you are
completely sure something is known, always speak up.  Even dupes
are sometimes useful because they help to adjust priorities.

> I was investigating mdocml on a Solaris 10 (X86_64) system and
> discovered that the latest release does not compile, but the latest
> CVS 2015-04-01 does :-) Many thanks to those responsible!

You are welcome.  That would be me, various people reporting issues,
and the friendly folks from OpenCSW who provide testing opportunities
on their build cluster.

> My testing shows that Solaris 10's regcomp() can not handle the
> character class used by mdocml's whatis(1): for example: the query
> 'whatis' generates "[[:<:]]whatis[[:>:]]" which gives the error
> "regcomp: invalid character class type", as shown below

I dimly remember hearing that before, and indeed [[:<:]] is not
required by POSIX but a BSD extension.

> Depending on the complexity, maybe a BSD version of regcomp() could be
> included with mdocml, to get the desired functionality and not have to
> reduce the functionality currently available to mdocml users.

Bundling a full regular expression library seems a bit much,
that code isn't exactly small.

> Alternatively, the code could make exceptions for broken (by the
> project's standards) regcomp() implementations.

Sounds better, i added an entry to the TODO list, see below.

Yours,
  Ingo


Log Message:
-----------
portability: word boundaries in regular expressions

Modified Files:
--------------
    mdocml:
        TODO

Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mdocml/mdocml/TODO,v
retrieving revision 1.203
retrieving revision 1.204
diff -LTODO -LTODO -u -p -r1.203 -r1.204
--- TODO
+++ TODO
@@ -488,6 +488,14 @@ are mere guesses, and some may be wrong.
   loc **  exist **  algo **  size *  imp **
 
 ************************************************************************
+* portability
+************************************************************************
+
+- word boundaries in regular expressions for whatis(1)
+  set up config tests to use [[:<:]], \<, or nothing
+  reminded by Peter Bray Fri, 03 Apr 2015 23:02:16 +1100
+
+************************************************************************
 * warning issues
 ************************************************************************
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

      reply	other threads:[~2015-04-03 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 12:02 Peter Bray
2015-04-03 12:52 ` Ingo Schwarze [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150403125259.GD7421@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mdocml.bsd.lv \
    --cc=pdb_ml@yahoo.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).