From: "André Aparício" <aparicio99@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] libbash - Progress report #11
Date: Tue, 7 Aug 2012 23:06:49 +0100 [thread overview]
Message-ID: <20120807230649.4eb89866@null> (raw)
Hi,
=== Progress of previous week ===
- Fix problem with an odd number of semicolons inside declare strings
- Support appending to a variable an unquoted string with special
characters like a minus
- Support implicit line break with a pipe at the end of the line
- Support function names starting with a keyword
=== Plan for this week ===
Now there's 8 (from 197) eclasses left with parsing problems, that
corresponds to 5 specific problems to fix.
- Fix problem with an odd number of single quotes inside here document
(couldn't solve this in the previous week)
- Fix variable substitution after variable attribution
- Support variable operator in builtin tests
- Support command substitution inside other command substitution
- Fix unwanted line continuation in comments
I've already worked with some of this before, but they're not trivial
to solve, so they were left for the end and I will try now to solve
them.
https://github.com/Aparicio99/libbash
Best regards,
André Aparício
reply other threads:[~2012-08-08 0:05 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=20120807230649.4eb89866@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