public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>,
	       "'Jan Kratochvil'" <jan.kratochvil@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [patch 2/2] iFort compat.: case insensitive symbols (PR 11313)
Date: Mon, 08 Nov 2010 17:18:00 -0000	[thread overview]
Message-ID: <000301cb7f68$e39a07c0$aace1740$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20101108163544.GB2933@adacore.com>

  Yes, I don't like the idea of lowercas'ing everything at
read-in: 
  In Free Pascal, despite the fact that pascal is case insensitive
at source level, uses internal functions
that are lowercase as opposed to all source declared function
which are uppercased.
  If we unconditionally lowercase everything, we would
possibly not be able anymore to specifically target those internal
functions.

  A while ago, I proposed a patch that changed the
used a second copy of the pascal name
http://sourceware.org/ml/gdb-patches/2010-04/msg00967.html

  But you didn't like that proposition ...
  I didn't reply to the last message in this thread,
but I now think that your proposal of using a specific
syntax (gdb) print <My_variable>
to avoid case conversion, would not work
for info command, which was one of the
reasons of that patch.

Pierre Muller

Pascal language maintainer

> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : lundi 8 novembre 2010 17:36
> À : Jan Kratochvil
> Cc : gdb-patches@sourceware.org
> Objet : Re: [patch 2/2] iFort compat.: case insensitive symbols (PR
> 11313)
> 
> > Therefore GDB will now lowercase any case insensitive symbol names on
> > their read-in from DWARF.
> 
> Just a thought, since I don't really know what this would entail, but
> shouldn't we just fix the lookup routines instead? I think that would
> be cleaner.
> 
> --
> Joel

  parent reply	other threads:[~2010-11-08 17:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-07  3:50 Jan Kratochvil
2010-11-08 16:36 ` Joel Brobecker
2010-11-08 17:02   ` Jan Kratochvil
2010-11-08 18:31     ` Joel Brobecker
2010-11-22  3:54       ` Jan Kratochvil
2010-11-22 18:54         ` Joel Brobecker
2010-11-22 19:19           ` Jan Kratochvil
2010-11-22 19:30             ` Joel Brobecker
2010-11-22 19:44               ` Jan Kratochvil
2010-11-22 19:57                 ` Joel Brobecker
2010-11-24 18:53                 ` Tom Tromey
2010-11-24 19:22                   ` Jan Kratochvil
2010-11-24 20:01                     ` Tom Tromey
2010-11-24 20:08                       ` Joel Brobecker
2010-11-24 21:37                         ` Tom Tromey
2010-11-24 21:45                           ` Jan Kratochvil
2010-11-24 21:55                             ` Tom Tromey
2010-11-24 20:17                       ` Jan Kratochvil
2010-11-24 20:31                         ` Joel Brobecker
2010-11-24 20:58                           ` Jan Kratochvil
2011-04-08 17:59         ` obsolete: " Jan Kratochvil
2010-11-08 17:18   ` Pierre Muller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-11-07  3:50 [patch 1/2] Code cleanup: New init_one_comp_unit Jan Kratochvil
2010-11-12 18:36 ` Tom Tromey
2010-11-12 18:43   ` Jan Kratochvil
2010-11-12 18:46     ` Tom Tromey
2010-11-16  4:37       ` Jan Kratochvil

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='000301cb7f68$e39a07c0$aace1740$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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).