Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77012 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 680 invoked from network); 1 Sep 2014 17:07:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Sep 2014 17:07:44 -0000 Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:39124] helo=h1123647.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DD/10-33940-ED7A4045 for ; Mon, 01 Sep 2014 13:07:42 -0400 Received: by h1123647.serverkompetenz.net (Postfix, from userid 33) id 4C0A36D209D; Mon, 1 Sep 2014 19:07:39 +0200 (CEST) Received: from 79.197.69.100 (SquirrelMail authenticated user anatol@belski.net) by webmail.klapt.com with HTTP; Mon, 1 Sep 2014 19:07:39 +0200 Message-ID: <30b36d3944d6cfb3b2dfaafbf41cc69c.squirrel@webmail.klapt.com> In-Reply-To: References: <2afc5a878ff4c780c74f4604f77525c1.squirrel@webmail.klapt.com> <3bc533250c01664354fce3e4167ca78b.squirrel@webmail.klapt.com> Date: Mon, 1 Sep 2014 19:07:39 +0200 To: "Dmitry Stogov" Cc: "Anatol Belski" , "Pierre Joye" , "PHP internals" , "Nikita Popov" , "Xinchen Hui" User-Agent: SquirrelMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Re: 64 bit string offsets From: anatol.php@belski.net ("Anatol Belski") Hi Dmitry, On Mon, September 1, 2014 16:17, Dmitry Stogov wrote: > Hi Anatol, > > > what do you mean? heap allocated structure? I think, it's not a good > option :( > > I didn't have time to think about this yet. > I thought about creating an extended zend_string struct with an appended offset member. Pointer to that structure could be injected into _zend_value and were compatible with the normal zend_string and would be used only for the offset case. But then, we could get rid of u2.str_offset and change the meaning of the IS_STR_OFFSET related macros. That struct could be initialized the same way as any other in an opcode. However I have yet to figure out where in the compiler this has to happen (somewhere near the zend_compile_assign() i suppose). Regards Anatol