Hello Antoine (other),<br /><br />&gt; 

If you have code in pure C with variables on the stack no malloc, doing a check of the coinbase size after the socket read can be certainly more robust than checking a non-null pointer. <br /><br />Can you please clarify this for me? When you say "non-null pointer" do you mean C pointer or transaction input "null point" (sequence of 32 repeating 0x00 bytes and 4 0xff)? What do you mean by "more robust"?<br /><br />Thanks,<br />Eric<br /><br />

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoindev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/bitcoindev/26b7321b-cc64-44b9-bc95-a4d8feb701e5n%40googlegroups.com?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/bitcoindev/26b7321b-cc64-44b9-bc95-a4d8feb701e5n%40googlegroups.com</a>.<br />