HGKeeper

Make PurplePluginProtocolInfo definitions consistent
release-2.x.y
2020-05-20, David Woodhouse

159344ba2a49

Make PurplePluginProtocolInfo definitions consistent

Since we can't use C99 structure initialisers, we have to manually add
new NULL fields to all protocols whenever we extend the structure.

Make it slightly easier to script that, by making the current last
field (get_cb_alias) consistent in all cases. In particular, there's
no reason *not* to have the trailing comma, as most already do.

Now I can add a new field to the PRPL by doing something like this...

PROTOFILES=`grep -rl '[A-Za-z_][A-Za-z0-9_]*,[[:space:]]*/\* get_cb_alias \*/' libpurple/protocols/ `
sed '/\/\* get_cb_alias \*\//{p;s/[A-Za-z_][A-Za-

/** @page log-signals Log Signals

@signals

@signal log-timestamp

@endsignals

@see log.h

<hr>

@signaldef log-timestamp

@signalproto

char *(*log_timestamp)(PurpleLog *log, time_t when, gboolean show_date);

@endsignalproto

@signaldesc

Emitted to allow plugins to customize the timestamp on a message

being logged.

@param log The log the message belongs to.

@param when The time to be converted to a string.

@param show_date Whether the date should be displayed.

@return A textual representation of the time, or @c NULL to use a

default format.

@note Plugins must be careful of logs with a type of PURPLE_LOG_SYSTEM.

@endsignaldef

// vim: syntax=c.doxygen tw=75 et

qulogic/pidgin