From: "André Aparício" <aparicio99@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] libbash - Progress report #8
Date: Tue, 17 Jul 2012 02:26:34 +0100 [thread overview]
Message-ID: <20120717022634.79947c87@null> (raw)
Hi,
=== Progress of previous week ===
Fixed things that were broken in some eclass.
- Escape '[' and ']' on command arguments
- Support local declarations inside eval
I worked on fixing two other things, function names starting with
keywords, and line-continuation on comments, but it didn't work out,
so they will be left for now.
=== Plan for this week ===
Search for more things to fix as before, but for now I have found a bug
in the array declaration, so I will start with this.
Some eclass files have the most interesting use of bash, so it still
needs some work until we can interpret everything correctly.
https://github.com/Aparicio99/libbash
Best regards,
André Aparício
reply other threads:[~2012-07-17 3:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120717022634.79947c87@null \
--to=aparicio99@gmail.com \
--cc=gentoo-soc@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox