From: Serbinenko Vladimir <serbinenko.vova@list.ru>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Pre-alpha scripting engine
Date: Thu, 20 Jan 2005 18:10:17 +0100 [thread overview]
Message-ID: <41EFE5F9.2020202@list.ru> (raw)
In-Reply-To: <87acr5ccq4.fsf@yahoo.it>
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.
next prev parent reply other threads:[~2005-01-20 17:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CpUhp-000IYX-00.grub-devel-bounces+serbinenko-vova=list-ru-gnu-org@mx11.mail.ru>
2005-01-14 18:48 ` Pre-alpha scripting engine Serbinenko Vladimir
2005-01-18 18:55 ` Marco Gerards
2005-01-18 19:54 ` Serbinenko Vladimir
2005-01-19 13:01 ` Marco Gerards
2005-01-19 20:04 ` Yoshinori K. Okuji
2005-01-19 20:48 ` Marco Gerards
2005-01-19 21:48 ` Maurizio Boriani
2005-01-20 17:10 ` Serbinenko Vladimir [this message]
2005-01-20 17:56 ` Yoshinori K. Okuji
2005-01-20 18:34 ` Serbinenko Vladimir
2005-01-21 2:26 ` Hollis Blanchard
2005-01-21 17:23 ` Scripting, partitions and filesystems Serbinenko Vladimir
2005-01-21 17:52 ` Device syntax, scripting, " Serbinenko Vladimir
2005-01-23 14:22 ` Pre-alpha scripting engine Yoshinori K. Okuji
2005-01-19 20:59 ` Tomas Ebenlendr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41EFE5F9.2020202@list.ru \
--to=serbinenko.vova@list.ru \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.