From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: ** X-Spam-Status: No, score=2.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,HDRS_MISSP autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 10085 invoked from network); 20 Oct 2021 12:59:20 -0000 Received: from hurricane.the-brannons.com (216.252.162.32) by inbox.vuxu.org with ESMTPUTF8; 20 Oct 2021 12:59:20 -0000 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by hurricane.the-brannons.com (OpenSMTPD) with ESMTP id cc4099fa for ; Wed, 20 Oct 2021 05:59:15 -0700 (PDT) Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [2001:558:fe21:29:69:252:207:41]) by hurricane.the-brannons.com (OpenSMTPD) with ESMTPS id b6723825 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO) for ; Wed, 20 Oct 2021 05:59:10 -0700 (PDT) Received: from resomta-ch2-16v.sys.comcast.net ([69.252.207.112]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id d9ylmnQE1kWizdBBUmQLRm; Wed, 20 Oct 2021 12:59:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1634734748; bh=Cy4v5C7zljXR3N2nQ59NOWwJJqUWfX9vnn6UksrjyGE=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=RHxaLXjN9/lyKeo3T94v6Nk+DOGlRj9pnRsz91k1Drn2S+fukYD7MrWTAT03bSikb OmaAhUEEHX60NZo00M3/A2ReIGTfcHEfwId2e+NmI5PnW6S072U8SnJ6+KxRSOmkzh ZZw5lXNjMsNg9m7nFYIoLgcx92R7sy40iBaJGWAtXX6jHAv/wu/tfB4IoVsiWxiluy oqKsdhLul5BeyIzdLYyTqqRMHbVTHFirVLWwCR8YJy90Erof0s4sUSElooOKNoGWwf vdgs9AoVvS2PAbjbangWR/wziSFMjURfXJZmxWNme/223cm9NyPeRkUwJyP6cAgtd4 1I2Fz+soOkSmA== Received: from unknown ([IPv6:2601:408:c300:a3d0::733d]) by resomta-ch2-16v.sys.comcast.net with ESMTPSA id dBBTm2SgPILBkdBBTm74ST; Wed, 20 Oct 2021 12:59:07 +0000 X-Xfinity-VMeta: sc=0.00;st=legit To:edbrowse-dev@edbrowse.org From: Karl Dahlke Reply-to: Karl Dahlke References: User-Agent: edbrowse/3.8.0+ Subject: possible root cause in gebcn for a recaptcha issue Date: Wed, 20 Oct 2021 08:59:06 -0400 Message-ID: <20210920085906.eklhad@comcast.net> X-BeenThere: edbrowse-dev@edbrowse.org List-Id: Edbrowse Development List Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit > Could this be done with a getter/setter concept? Not directly. getter is on the property of an object, not a single variable. foo.bar invokes a getter every time you reference it, but if you just say x = blah x is no longer a getter, it might be the result of a getter but it is what it is. Indirectly, imagine x being an object with getters on the object, lots of them. Like all the array methods, they first populate x, according to its original call, then invoke the array method. That's fine but what about the simple x[3] Am I supppose to put a getter on 3, to repopulate the list and make sure I'm returning item 3? Should I do that for every possible integer? That's not practical! So as I say, I don't know how to do it. Karl Dahlke