[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [coldsync-hackers] Undeclared variables from Palm modules
- To: coldsync-hackers at lusars dot net
- Subject: Re: [coldsync-hackers] Undeclared variables from Palm modules
- From: coldsync-hackers at oldach dot net (Helge Oldach)
- Date: Mon, 8 Apr 2002 19:26:33 +0200 (CEST)
- In-Reply-To: <006301c1df14$316001c0$3200a8c0@jecinc.on.ca> from Brian Johnson at "Apr 8, 2002 11:43:53 am"
- Reply-To: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
Brian Johnson:
> Not being a programmer, I don't know if there is a reason why the Palm
> modules don't return anything for null fields
>
> I do know that it is a pain to check if the value exists before I can use it
> in a comparison
>
> Can the Palm modules be changed to avoid unitialized variable errors or have
> I created my own problems while trying to add records?
There is a difference between a Null (i.e. empty) value and a
non-existing (i.e. undefined) value. We would lose functionality if
everything were Null by default.
Helge
--
This message was sent through the coldsync-hackers mailing list. To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body. For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.