public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Jaben Carsey <jaben.carsey@intel.com>
To: edk2-devel@lists.01.org
Subject: [PATCH v1 0/9] BaseTools: refactor variables and regular expressions
Date: Fri, 16 Mar 2018 16:27:37 -0700	[thread overview]
Message-ID: <cover.1521242771.git.jaben.carsey@intel.com> (raw)

change how regular expressions and variables are used to maximize sharing 
during build

Jaben Carsey (9):
  BaseTools: FdfParser and FdfParserLite share reg exp
  BaseTools: GlobalData share same MACRO name definition
  BaseTools: add GUID pattern to global data
  BaseTools: use new shared GUID regular expressions
  BaseTools: Regular Expressions refactor out the hex char for later
    reuse
  BaseTools: Add new RegExp for future use
  BaseTools: Use precompiled RegExp
  BaseTools: GlobalData Add a regular expression for a hex number
  BaseTools: remove local hex number regular expression

 BaseTools/Source/Python/AutoGen/UniClassObject.py |  4 ++--
 BaseTools/Source/Python/Common/Expression.py      |  6 ++----
 BaseTools/Source/Python/Common/FdfParserLite.py   | 10 +++++-----
 BaseTools/Source/Python/Common/GlobalData.py      | 21 +++++++++++++++++---
 BaseTools/Source/Python/Common/RangeExpression.py | 19 ++++++++----------
 BaseTools/Source/Python/GenFds/FdfParser.py       |  5 ++---
 6 files changed, 37 insertions(+), 28 deletions(-)

-- 
2.16.2.windows.1



             reply	other threads:[~2018-03-16 23:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 23:27 Jaben Carsey [this message]
2018-03-16 23:27 ` [PATCH v1 1/9] BaseTools: FdfParser and FdfParserLite share reg exp Jaben Carsey
2018-03-28 13:05   ` Zhu, Yonghong
2018-03-16 23:27 ` [PATCH v1 2/9] BaseTools: GlobalData share same MACRO name definition Jaben Carsey
2018-03-16 23:27 ` [PATCH v1 3/9] BaseTools: add GUID pattern to global data Jaben Carsey
2018-03-16 23:27 ` [PATCH v1 4/9] BaseTools: use new shared GUID regular expressions Jaben Carsey
2018-03-16 23:27 ` [PATCH v1 5/9] BaseTools: Regular Expressions refactor out the hex char for later reuse Jaben Carsey
2018-03-16 23:27 ` [PATCH v1 6/9] BaseTools: Add new RegExp for future use Jaben Carsey
2018-03-16 23:27 ` [PATCH v1 7/9] BaseTools: Use precompiled RegExp Jaben Carsey
2018-03-16 23:27 ` [PATCH v1 8/9] BaseTools: GlobalData Add a regular expression for a hex number Jaben Carsey
2018-03-16 23:27 ` [PATCH v1 9/9] BaseTools: remove local hex number regular expression Jaben Carsey

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-list 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=cover.1521242771.git.jaben.carsey@intel.com \
    --to=devel@edk2.groups.io \
    /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