Path: ...!fu-berlin.de!uni-berlin.de!not-for-mail
From: ram@zedat.fu-berlin.de (Stefan Ram)
Newsgroups: comp.lang.python
Subject: Re: Correct syntax for pathological re.search()
Date: 21 Oct 2024 20:24:49 GMT
Organization: Stefan Ram
Lines: 21
Expires: 1 Jul 2025 11:59:58 GMT
Message-ID: <functional-20241021212324@ram.dialup.fu-berlin.de>
References: <ve0o34$1nep4$1@dont-email.me> <MQaOO.3313338$EVn.2054758@fx04.ams4> <011301db1c22$5e7519c0$1b5f4d40$@gmail.com> <20241012105958.cbctekv7vustleha@hjp.at> <966b510d-9bd7-4472-a858-7e042d78461d@tompassin.net> <20241018210941.f5azh2lvz7cxzcy5@hjp.at> <mailman.28.1729285790.4695.python-list@python.org> <veumlu$3gfsk$1@dont-email.me> <20241021191049.iclg7pmpfrpkel55@hjp.at> <mailman.29.1729537858.4695.python-list@python.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: news.uni-berlin.de OZhM2b6nRE/7ow7stivsqAFWOhl+JrWfZlBWl+mQycCo4j
Cancel-Lock: sha1:iBtssjD4FIrURomhuqSojXN0ZOk= sha256:IlhS9nXbtThwg3WlOk2GgKvZ9TlFh3ldHKxD2fYh9Tc=
X-Copyright: (C) Copyright 2024 Stefan Ram. All rights reserved.
	Distribution through any means other than regular usenet
	channels is forbidden. It is forbidden to publish this
	article in the Web, to change URIs of this article into links,
        and to transfer the body without this notice, but quotations
        of parts in other Usenet posts are allowed.
X-No-Archive: Yes
Archive: no
X-No-Archive-Readme: "X-No-Archive" is set, because this prevents some
	services to mirror the article in the web. But the article may
	be kept on a Usenet archive server with only NNTP access.
X-No-Html: yes
Content-Language: en-US
Bytes: 2483

"Peter J. Holzer" <hjp-python@hjp.at> wrote or quoted:
>On 2024-10-19 00:15:23 +0200, jak via Python-list wrote:
>>Allow me to be fussy: r"\\sout{" and r"\\sout\{" are similar but not
>>equivalent.
.. . .
>Yes, that's the parser. But the result of parsing will be the same:
>The string will end in a literal backslash.

  Functional reqs lay out what your system's got to do, while
  non-functional reqs are all about time and other resource
  constraints.

  When you're crunching through parsing, what pops out is
  your functional bread and butter.

  But the time it takes to chew through that data?
  That's non-functional and implementation-dependent territory.

  So, we can say they're functionally equivalent.