Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v1 03/13] script language API for GDB: python.[ch] changes
Date: Fri, 06 Dec 2013 17:22:00 -0000	[thread overview]
Message-ID: <m338m5zyho.fsf@sspiff.org> (raw)
In-Reply-To: <52A1C475.4010901@redhat.com> (Phil Muldoon's message of "Fri, 06	Dec 2013 12:35:01 +0000")

Phil Muldoon <pmuldoon@redhat.com> writes:
>> +
>> +extern int gdbpy_auto_load_enabled (const struct script_language_defn *);
>> +
>> +/* script_language_ops "methods".  */
>> +
>> +extern int gdbpy_apply_val_pretty_printer
>> +  (const struct script_language_defn *,
>> +   struct type *type, const gdb_byte *valaddr,
>> +   int embedded_offset, CORE_ADDR address,
>> +   struct ui_file *stream, int recurse,
>> +   const struct value *val,
>> +   const struct value_print_options *options,
>> +   const struct language_defn *language);
>> +extern enum script_bt_status gdbpy_apply_frame_filter
>> +  (const struct script_language_defn *,
>> +   struct frame_info *frame, int flags, enum script_frame_args args_type,
>> +   struct ui_out *out, int frame_low, int frame_high);
>> +extern void gdbpy_preserve_values (const struct script_language_defn *,
>> +				   struct objfile *objfile,
>> +				   htab_t copied_types);
>> +extern enum scr_bp_stop gdbpy_breakpoint_cond_says_stop
>> +  (const struct script_language_defn *, struct breakpoint *);
>> +extern int gdbpy_breakpoint_has_cond (const struct script_language_defn *,
>> +				      struct breakpoint *b);
>
> I did not ask in the previous patch, but why could not these functions
> have been kept in Python?

Not sure I understand the question.  Can you elaborate?

>>  
>> +/* Some code (e.g., MI) wants to know if a particular scripting language
>> +   successfully initialized.
>> +   Return non-zero if Python scripting successfully initialized.  */
>> +
>> +int
>> +script_lang_python_initialized (void)
>> +{
>> +  if (script_language_python.ops != NULL)
>> +    return script_language_python.ops->initialized (&script_language_python);
>> +  return 0;
>> +}
>> +
>
> I missed the convention here, but I thought that methods exported to
> the ops struct had a gdbpy_ prefix?

This one isn't exported through the ops struct.

OTOH, as noted in an earlier email, a better way to go would be
a general function that took a script_lang enum as an argument.


      reply	other threads:[~2013-12-06 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06  5:52 xdje42
2013-12-06  9:43 ` Phil Muldoon
2013-12-06 17:19   ` Doug Evans
2013-12-06 12:35 ` Phil Muldoon
2013-12-06 17:22   ` Doug Evans [this message]

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=m338m5zyho.fsf@sspiff.org \
    --to=xdje42@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@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