[943] in Coldmud discussion meeting

root meeting help first first in chain previous in chain previous next last

Re: [COLD] regular expressions

daemon@ATHENA.MIT.EDU (Sat Mar 23 17:18:33 1996 )

Date: Sat, 23 Mar 1996 14:58:19 -0700 (MST)
From: Brandon Gillespie <brandon@tombstone.sunrem.com>
To: Jeff Kesselman <jeffk@tenetwork.com>
cc: coldstuff@cold.org, Miroslav Silovic <silovic@srce.hr>
In-Reply-To: <199603230019.QAA06011@yam.tenetwork.com>

> >I think we should use Perl regexp (if you feel like isolating its
> >source). At least I can tell which characters need to be backslashed and
> >when in Perl regexp. :) It's also somewhat standard and powerful
> >enough.
> As I understand it, the issue is not changing what regexp in coldc 
> does, but how itis implemented, yes?

Basically, yeah.  Actually, I was wandering through the FreeBSD kernel 
and stumbled across the regexp code and was wondering if we should just 
link into the POSIX regexp code (if it exists), or if we should ignore it 
(as we do now).

> I personally like coldc 's regexp for the way it allows me to specify 
> what I want extracted.  Its very mud-friendly.  How it is implemented 
> I don't care so much about BUT the same expression should produce the 
> same reult on all ColdX implementations.  How it does it IMO shoudl 
> be left up to the porter/implementor.

Yup, this is the concern I brought up, the current POSIX regexp definition
is vague in areas, leaving much open for interpretation.  In general this 
isn't a problem, but there are areas where certain things could vary from 
OS to OS.