Re: [Discuss-gnuradio] Introduction for GSoC participation

[Marcus Müller]

Hi Arpit,

thanks for reaching out and sorry it took us so long to react!
Then, just a super-small advice: we're quite informal here, so we'd
normally not address each other as "Sir"; makes little sense, because
there's enough Ladies in the GNU Radio community, too, for example! :)
But thanks for being so respectful.

An "abstract representation" in the context of parsing is typically a
/data structure/ such as a tree that you can directly work with, in
contrast to e.g. the original text file.

Generally, I'd recommend you do not try to write your own C++ parser –
there's plenty of those already, it's a hard job, and there's no reason
to reinvent the wheel:
All compilers and all code linters already have something like that.
For example, the clang compiler suite (which is the default compiler
for anything that Apple produces, and Google is probably using it a
lot, too, and I do use it myself, too) is very much meant to be usable
as a /library/! That means it should be "simple" to just use libclang,
and you can use that from Python, too[1].

What to do next?

Before you start working on the project, might be a good idea to
introduce yourself to the mailing list!
To apply for the GSoC project, you'll have to write a /proposal/ in the
end – something that shows what you're planning to do, how much time to
spend on what, and effectively gives a rundown of what you want to do
in which week of the active GSoC phase. Writing that proposal is a lot
of work, so I'd recommend starting out by trying to mentally structure
how to divide the overall problem in smaller problems, and what you
want to deliver finally!
That will certainly raise a lot of questions, and you could discuss
these with the mailing list.
Then, you'd write your proposal.

Best regards,
Marcus

[1] 
https://eli.thegreenplace.net/2011/07/03/parsing-c-in-python-with-clang

On Fri, 2019-03-01 at 03:27 +0530, Arpit Gupta wrote:
> Hello everyone!
> I have started working on block header parsing tool project for GSoC.
> I'm currently experimenting with header (.h) files to find out
> patterns in them, parsing them, thus getting out most of the useful
> information.
> I was thinking of extending gr_modtool because of the CLI, which
> would thus take input as a header file and output an abstract
> representation for that on the terminal itself and thus generating
> YAML files.
> But I am not sure with the meaning of abstract representation. Is it
> that I have to provide the parsed information in a readable format
> for that header file?
> Sir, if you can please guide me with what to do next, I will be
> highly thankful.
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio