|How to Optimize a Black Box email@example.com (Seima Rao) (2017-03-24)|
|Re: How to Optimize a Black Box firstname.lastname@example.org (Kaz Kylheku) (2017-03-24)|
|Re: How to Optimize a Black Box email@example.com (George Neuner) (2017-03-24)|
|From:||Seima Rao <firstname.lastname@example.org>|
|Date:||Fri, 24 Mar 2017 12:22:56 +0530|
|Injection-Info:||miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="47587"; mail-complaints-to="email@example.com"|
|Keywords:||optimize, question, comment|
|Posted-Date:||24 Mar 2017 16:09:03 EDT|
In our software development process, we decided that we will
be using Open Source libraries as a plug-in into our software.
Permissive licenses like BSD, MIT & Apache allow us
some freedom in redistributing the code for commercial purposes.
However, when cutting across licensing options, one is often
held due to a library(Open Source) as a black box.
Since we are plugging in a third party library, at some point
of time in the future, we envision visiting it to optimize
starting with the hotpath and then meandering into
the visible items in a profile.
My question is how do we start at all in optimizing a black box ?
Because these open source initiatives have become synonymous
with business (someone using them for commercial purposes) in
many countries, I suspect that many have felt the need to
"peek inside" as well as "work from the outside".
Can anyone help ?
p.s. Rewrite is an option but still ...
[I don't understand the problem. With every open source licence I've
ever seen, if you can use the code at all, you've got the source code
and you can recompile it and optimize it. -John]
Return to the
Search the comp.compilers archives again.