diff options
| author | Andrew Burgess <andrew.burgess@embecosm.com> | 2020-10-20 13:41:18 +0100 |
|---|---|---|
| committer | Andrew Burgess <andrew.burgess@embecosm.com> | 2020-12-23 20:53:14 +0000 |
| commit | 76ca72bc5b72ac0bbab239bda41cd61f6cb7d051 (patch) | |
| tree | b2d64c1c54b6af4d5d0d8dcf2bcc64e8a4c000be /gdb/f-lang.h | |
| parent | c5ee319e6cc7a02d35871896e8205e1f782fbc00 (diff) | |
| download | gdb-76ca72bc5b72ac0bbab239bda41cd61f6cb7d051.zip gdb-76ca72bc5b72ac0bbab239bda41cd61f6cb7d051.tar.gz gdb-76ca72bc5b72ac0bbab239bda41cd61f6cb7d051.tar.bz2 | |
gdb: remove LA_EMIT_CHAR macro
Now that every use of the LA_EMIT_CHAR macro is within a language_defn
member function we can simply call the emitchar member function
directly instead of using the LA_EMIT_CHAR macro.
If we are ever inside a language object, for example, cplus_language,
while current_language points at something other than cplus_language
then this commit will result in a change in behaviour. However, I
believe if we did have such a difference then this would be a bug in
GDB. AS such I'm going to claim there _should_ be no user visible
changes from this commit.
gdb/ChangeLog:
* c-lang.c (language_defn::printchar): Call emitchar, not
LA_EMIT_CHAR.
* f-lang.h (f_language::printchar): Likewise.
* language.h (LA_EMIT_CHAR): Delete macro.
* rust-lang.c (rust_language::printchar): Call emitchar, not
LA_EMIT_CHAR.
Diffstat (limited to 'gdb/f-lang.h')
| -rw-r--r-- | gdb/f-lang.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/f-lang.h b/gdb/f-lang.h index 351f219..51ee6f6 100644 --- a/gdb/f-lang.h +++ b/gdb/f-lang.h @@ -155,7 +155,7 @@ public: struct ui_file *stream) const override { fputs_filtered ("'", stream); - LA_EMIT_CHAR (ch, chtype, stream, '\''); + emitchar (ch, chtype, stream, '\''); fputs_filtered ("'", stream); } |