Okay so,

(a) describing it as - 'terminating null character' (in place of NUL) is fine.
(b) w.r.t the NULL pointer, iam fine with either describing it as 'NULL' alone 
or 
desribing it as 'NULL pointer' both are fine with me.

In the SAF CPROG guide, 'null character' and 'NULL' are used during above cases 
respectively.

Mathi

----- [email protected] wrote:

> Actually, now that I look at the document I realize that I should not
> 
> write "NULL pointer". I should either write "null pointer" or simply 
> "NULL", since NULL means "null pointer". :-)
> 
> Maybe it is better if I always write "null character" and "null
> pointer"?
> 
> / Anders Widell
> 
> On 10/03/2014 02:39 PM, Mathivanan Naickan Palanivelu wrote:
> > It's an ack,
> >
> > I had understood the differentiation you wanted to make, but i
> wanted the document
> > to sound more SAF like language.
> >
> > Thanks,
> > Mathi.
> >
> >
> > ----- [email protected] wrote:
> >
> >> Hi!
> >>
> >> Is that an ack?
> >>
> >> Note: I wrote NUL at some places and NULL at other places. NUL is
> not
> >>
> >> misspelt - it is the name (abbreviation) of the null character
> (i.e.
> >> '\0' in the C language). NULL refers to a null pointer (i.e.
> (void*)0
> >> in
> >> the C language).
> >
> >
> >> / Anders Widell
> >>
> >> On 10/03/2014 02:13 PM, Mathivanan Naickan Palanivelu wrote:
> >>> Made some trivial editorial changes.
> >>>
> >>> Mathi.
> >>>
> >>> ----- [email protected] wrote:
> >>>
> >>>> Hi!
> >>>>
> >>>> I have added chapter 4, describing the extended SaNameT type.
> >> Document
> >>>> is attached.
> >>>>
> >>>> / Anders Widell

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-devel

Reply via email to