From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Slot accessing issues in EIEIO Date: Wed, 06 May 2020 23:39:06 -0400 Message-ID: References: <87a72lhf3b.wl-all_but_last@163.com> <878si5gmt7.wl-all_but_last@163.com> <877dxoh1m6.wl-all_but_last@163.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="42031"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Zhu Zihao Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu May 07 05:39:46 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jWXNx-000Ap3-Db for ged-emacs-devel@m.gmane-mx.org; Thu, 07 May 2020 05:39:45 +0200 Original-Received: from localhost ([::1]:43712 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jWXNw-0000q2-Fr for ged-emacs-devel@m.gmane-mx.org; Wed, 06 May 2020 23:39:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45500) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jWXNP-0000M9-0y for emacs-devel@gnu.org; Wed, 06 May 2020 23:39:11 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:63799) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jWXNO-00061V-CM for emacs-devel@gnu.org; Wed, 06 May 2020 23:39:10 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 94FCE450A17; Wed, 6 May 2020 23:39:09 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 233F345095A; Wed, 6 May 2020 23:39:08 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1588822748; bh=8CowzwGTclUWgvwiJbHsBOGX/+EQinFEK1y44r+NqGc=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=mie6xLU2UmsFXDCxPtGlVecJjF3L037ZazGyR+ND8tGS79ELVCea6vo+MGGv34BAL 1zfclLqOfT5g7kP+iMe2DWIKNdJZkWAXHsOUyU1kZ5EcDjL26VguF5FK9b9ylJEo2R NYpTHNgdY5x97UOvI22OaF0D1+i21iNVnO4ekoer8zPcG3pNLiy5DW3XSRNgOkpoye gBCEuFrUEzChN+RnPmkYjKhrVyAkh1Tfc4fIbQcoHneqIO1/9wir/5ikZ+oyY213p2 Mon/ltkQ2FeW1KXsDp6GiylDMJ7lRdv1qhmf0fp2TM7Upq+kMwYcLaqbEQLf/ClieF gLT/ikc1pt+Zg== Original-Received: from alfajor (unknown [216.154.3.202]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id D964D1202A1; Wed, 6 May 2020 23:39:07 -0400 (EDT) In-Reply-To: <877dxoh1m6.wl-all_but_last@163.com> (Zhu Zihao's message of "Thu, 07 May 2020 11:20:49 +0800") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/06 23:12:36 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:249148 Archived-At: > slot-missing just work, but I don't think it gets things done right. > > If we use slot-missing. We have to manage the column names manually instead of > present them in slots. We should keep the proxy object doesn't have any > slot to make slot-missing work, or your slot name may collide with SQL column > name. You're going too fast here: I have no idea what slots there are currently in the object, why they're there, what kind of slots the `slot-missing` thingy would catch, what is the relation between the "real" slots and the others, ... In the current solution, when there is a name collision between a "real" slot and a non-real one, how is it resolved? > Thus, we have to give up the direct way to describe the structure of > SQL database. What is this "direct way" you apparently currently use? > when accessing a slot), I have to repeat the pattern I mentioned above. I haven't yet understood what this pattern is. Stefan