From: Giannis Nikiteas <giannis.nikiteas@gmail.com>
To: overseers@sourceware.org
Subject: GDB account: Fortran related issues
Date: Thu, 7 Jul 2022 09:24:59 +0100 [thread overview]
Message-ID: <aeecb3f1-4692-bb45-4b7a-669efb428c09@gmail.com> (raw)
Hi,
I hope this email finds you well. I was wondering if you could open an
account for me, or just file the issues/feature enhancements on my
behalf.The issues that I have been meaning to file are related to
Fortran, more specifically:
1. The Python API support for Fortran types (type printing) like
strings, arrays, variables defined with non-default kinds, is quite
limited and I was wondering if you could expand to allow for easier access.
2. More pretty printers for Fortran need to written e.g. type-bound
procedures, select type constructs and other Modern (2003+) features.
There are probably more Fortran GDB related issues, not present in
C/C++, but I think these two would greatly improve the Fortran + GDB
experience.
Implementing 1. would make 2. a lot easier to complete. I would be glad
to try and help on these issues, but I would probably need some help
setting up my workflow for testing changes to the GDB Python wrappers.
If you want help with regards to anything Fortran related you can reach
out to our community (where I am an active member):
https://fortran-lang.discourse.group/
Have a good day and thank you for your time.
Kind regards,
Giannis
--
------------------------------------------------------------------------
Ioannis Nikiteas <https://gnikit.github.io/>
PhD Candidate at Applied Modelling & Computation Group (AMCG)
<https://www.imperial.ac.uk/earth-science/research/research-groups/amcg/>
Department of Earth Science and Engineering
Imperial College London
next reply other threads:[~2022-07-07 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 8:24 Giannis Nikiteas [this message]
2022-07-07 10:42 ` Mark Wielaard
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=aeecb3f1-4692-bb45-4b7a-669efb428c09@gmail.com \
--to=giannis.nikiteas@gmail.com \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).