Received: with ECARTIS (v1.0.0; list gopher); Wed, 20 Mar 2002 08:41:15 -0500 (EST) Return-Path: <jgoerzen@complete.org> Delivered-To: gopher@complete.org Received: from christoph.complete.org (unknown [168.215.193.254]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 637EF3B816 for <gopher@complete.org>; Wed, 20 Mar 2002 08:41:15 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by christoph.complete.org (Postfix) with ESMTP id 774215A461 for <gopher@complete.org>; Wed, 20 Mar 2002 08:41:17 -0500 (EST) Date: Wed, 20 Mar 2002 08:41:17 -0500 Subject: [gopher] Re: gopher 3.0.4 imminent Content-type: text/plain; charset=US-ASCII Mime-Version: 1.0 (Apple Message framework v481) From: John Goerzen <jgoerzen@complete.org> To: gopher@complete.org Content-Transfer-Encoding: 8bit In-Reply-To: <p05010400b8be3a463284@[205.189.158.32]> Message-Id: <274E6084-3C08-11D6-BC1E-0003930BF072@complete.org> X-Mailer: Apple Mail (2.481) X-archive-position: 507 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-ID: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

On Wednesday, March 20, 2002, at 08:11 AM, Robert Hahn wrote:

> That's quite the list. Thanks for your contributions.

Thanks!

> Now, while I haven't pulled a copy of 3.0.4 from CVS yet, I've a > question: I don't know how you did the rewrite, but I'd be interested > to know if the steps you took rewriting the code resulted in > rendering irrevalent the note about compiling in OS X under UFS...

No, they did not. However, I can still try to accomplish that.

Unfortunately, MacOS X is a nasty case because it doesn't behave like a Unix "should". I'm still uncertain why there even is a problem at all, because even with that behavior, the difference between #include "regex.h" and #include <regex.h> should do it. However, if necessarily, I will rename it for a future version.

-- John