From: Yordan Karadzhov <ykaradzhov@vmware.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org,
Yordan Karadzhov <ykaradzhov@vmware.com>
Subject: Re: [PATCH 2/4] kernel-shark-qt: Add KernalShark Utils
Date: Wed, 10 Oct 2018 18:27:53 +0300 [thread overview]
Message-ID: <008c5da4-1566-b588-180c-afa31b352eb2@vmware.com> (raw)
In-Reply-To: <20181009123419.22fe49f2@gandalf.local.home>
On 9.10.2018 19:34, Steven Rostedt wrote:
> Is this private to libkshark and not going to be exported?
>
> In other words, do we need to worry about namespace?
The namespace here is used mostly for making the code easy to read.
C++ people do this because it makes the code look more OO-ish.
Note that
namespace Foo
{
bool bar1(int x);
void bar2();
};
is equivalent to
class Foo {
static bool bar1(int x);
static void bar2();
};
Thanks!
Yordan
next prev parent reply other threads:[~2018-10-10 22:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 15:16 [PATCH 0/4] Add basic components to be used by the Qt GUI Yordan Karadzhov
2018-10-08 15:16 ` [PATCH 1/4] kernel-shark-qt: Add Qt as a third party dependency Yordan Karadzhov
2018-10-08 15:16 ` [PATCH 2/4] kernel-shark-qt: Add KernalShark Utils Yordan Karadzhov
2018-10-09 16:34 ` Steven Rostedt
2018-10-10 14:12 ` Yordan Karadzhov
2018-10-10 15:22 ` Steven Rostedt
2018-10-10 15:25 ` Yordan Karadzhov
2018-10-10 19:02 ` Steven Rostedt
2018-10-10 15:27 ` Yordan Karadzhov
2018-10-10 15:27 ` Yordan Karadzhov [this message]
2018-10-10 19:04 ` Steven Rostedt
2018-10-08 15:16 ` [PATCH 3/4] kernel-shark-qt: Add Widgets Lib Yordan Karadzhov
2018-10-09 16:42 ` Steven Rostedt
2018-10-08 15:16 ` [PATCH 4/4] kernel-shark-qt: Add widget demo example Yordan Karadzhov
2018-10-09 16:45 ` Steven Rostedt
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=008c5da4-1566-b588-180c-afa31b352eb2@vmware.com \
--to=ykaradzhov@vmware.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).