From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Crg4e-0002ND-AN for mharc-grub-devel@gnu.org; Thu, 20 Jan 2005 12:26:24 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Crg4Z-0002Kb-I2 for grub-devel@gnu.org; Thu, 20 Jan 2005 12:26:20 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Crg4T-0002HX-26 for grub-devel@gnu.org; Thu, 20 Jan 2005 12:26:13 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Crg4S-0002G6-SI for grub-devel@gnu.org; Thu, 20 Jan 2005 12:26:12 -0500 Received: from [194.67.23.121] (helo=mx1.mail.ru) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Crfoo-0006f0-Ex for grub-devel@gnu.org; Thu, 20 Jan 2005 12:10:02 -0500 Received: from [81.62.46.121] (port=1312 helo=[192.168.1.100]) by mx1.mail.ru with esmtp id 1Crfoj-0004Yl-00 for grub-devel@gnu.org; Thu, 20 Jan 2005 20:09:58 +0300 Message-ID: <41EFE5F9.2020202@list.ru> Date: Thu, 20 Jan 2005 18:10:17 +0100 From: Serbinenko Vladimir User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: The development of GRUB 2 References: <41ED6964.9010102@list.ru> <87oeflwp1n.fsf@marco.marco-g.com> <200501192104.41983.okuji@enbug.org> <87wtu9uouc.fsf@marco.marco-g.com> <87acr5ccq4.fsf@yahoo.it> In-Reply-To: <87acr5ccq4.fsf@yahoo.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam: Not detected Subject: Re: Pre-alpha scripting engine X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 17:26:22 -0000 Maurizio Boriani wrote: >The use of guile (as specified in gnu standards) as embedded language >should be a good choice :) but this is only an idea > >bye > > > The problem with guile is that it has no $ before variable which makes it difficult to integrate with shell. I discovered that bash and PHP can even coexist!! But I don't know bash very well so if I'm wrong please e-mail it. Now I'm rewriting the parser for easier integrating(thanks Marco). At the same time it'll be combined PHP/bash blocks detector Ambiguos operator I found is do in constuction like for (...) do ..; while(...); Can wcript end here? Is do ...; while (...); PHP or bash I propose folowing checking: if after ambiguos do there is operator and then while with ; it's PHP because in bash you have to write while (...) do ... If you really want that while is PHP but do is bash you can write for (...) do ..;; while(...); done; Other my idea is to introduce #!bash and #!php commands to switch languages ex: #!bash for (...) do ..; #!php while(...); #!bash done; Perhaps also #!auto. But in my realisation they won't restrict using of other language but simply set that ambiguos constructions are php or bash. What do you think about it all? Please mail any your idea.