public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC/PATCH] tools: New 'spl-stackusage' script
Date: Wed, 11 Feb 2015 10:12:08 +0100	[thread overview]
Message-ID: <54DB1CE8.4010008@gmail.com> (raw)
In-Reply-To: <20150211061546.4a1196a7@i7>

Hi Siarhei,

On 02/11/2015 05:15 AM, Siarhei Siamashka wrote:
> On Mon, 02 Feb 2015 14:15:33 +0100
> "Andreas Bie?mann" <andreas.devel@googlemail.com> wrote:

>> Another point ... I really appreciate your efforts to bring this tool
>> in. So don't get me wrong, but ... why ruby?
> 
> That's because I know ruby, but don't know python at the moment.

That's a good reason.

> Why I have picked ruby over python some years ago is another story.
> But I don't want to start a programming language holy war here :)
> 
>> A while ago some guys started to introduce python for some complex
>> scripts, before that u-boot only had shell scripts.
>> I personally think one interpreter in u-boot world is enough. I'm
>> curious how others think about that.
> 
> If python is a requirement, then I will have to learn it first. Which
> is fair enough. But this requirement first needs to be explicitly
> communicated by somebody.

For me it is not a real requirement, I'm fine with ruby when it works as
expected. The dynamic stack allocation should be considered in the tool
even though FAT would be converted to malloc(2) (some days ;).

Best regards

Andreas Bie?mann

      reply	other threads:[~2015-02-11  9:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31 23:47 [U-Boot] [RFC/PATCH] tools: New 'spl-stackusage' script Siarhei Siamashka
2015-02-02 13:15 ` Andreas Bießmann
2015-02-11  4:15   ` Siarhei Siamashka
2015-02-11  9:12     ` Andreas Bießmann [this message]

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=54DB1CE8.4010008@gmail.com \
    --to=andreas.devel@googlemail.com \
    --cc=u-boot@lists.denx.de \
    /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