[webkit-efl] Using 0 or NULL in public C headers documentation ?

Dumez, Christophe christophe.dumez at intel.com
Sun Jul 15 23:25:37 PDT 2012


At the moment, we using not consistent in the usage of NULL or 0 in the
documentation of our public C headers.

The best practice is not currently documented by:

However, Gyuyoung is telling me there is an "unspoken" rule for WebKit-EFL
port that we should use 0.
I personally disagree and I think we should *always* use NULL in our public
C headers.

While 0 is advised for null pointers in C++, it is not for C (
If you look at the EVAS documentation, it is also using NULL in its
documentation, not 0.

What do other WebKit EFL developers think?
We need to agree first, then document it on the coding style page and patch
the code accordingly.

For example,

 * Gets the Ewk_Settings of this view.
 * @param o the view object to get Ewk_Settings
 * @return the Ewk_Settings of this view or @c *NULL* on failure
 EAPI Ewk_Settings *ewk_view_settings_get(const Evas_Object *o);

Christophe Dumez
Linux Software Engineer, PhD
Intel Finland Oy - Open Source Technology Center
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-efl/attachments/20120716/e39e1570/attachment.html>

More information about the webkit-efl mailing list