Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
macOS & iOS Developer Playground
iOS Development
Xcode performance
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="SteveSawyer" data-source="post: 1921991" data-attributes="member: 415609"><p>Each language is unique in certain ways. But there seems to be a bit of convergence wrt syntax so that languages that you're not familiar with (unlike "C" which can be cryptic even to experienced folks) can still be followed, even though the nuances may be missed. I'm not familiar with the MBA acronym though...<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt=":unsure:" title="Unsure :unsure:" loading="lazy" data-shortname=":unsure:" /> What is that?</p><p></p><p>As to optionals, having written 95% of my code for database systems which have the option of defining fields as being able to accept NULL values (some DB's allow null values by default) so I well appreciate the value of variables/fields that can accept NULL values. As with any strongly-typed language, you have to be aware of trying to stuff an incompatible data type into a token. It's been a few years but IIRC both C# and Python variables can accept NULL values by default. I've been away from it for about 7 years, so I'm rusty. But it's <em>really</em> useful particularly in booleans where you can distinguish clearly between "Yes", "No" and "Don't know." I've seen programmers get themselves into very sticky corners by writing code that doesn't recognize NULL values. They design the DB (something most programmers don't have the training for) and don't allow NULL values on boolean fields, not wanting to deal with that additional complexity. Depending on the context, there can be a HUGE difference between "No" and "Don't know."</p><p></p><p>IAC, this is just hobby-level development. I'm in no rush, so if I have to wait until I have a beefier machine to work with it's NBD.</p></blockquote><p></p>
[QUOTE="SteveSawyer, post: 1921991, member: 415609"] Each language is unique in certain ways. But there seems to be a bit of convergence wrt syntax so that languages that you're not familiar with (unlike "C" which can be cryptic even to experienced folks) can still be followed, even though the nuances may be missed. I'm not familiar with the MBA acronym though...:unsure: What is that? As to optionals, having written 95% of my code for database systems which have the option of defining fields as being able to accept NULL values (some DB's allow null values by default) so I well appreciate the value of variables/fields that can accept NULL values. As with any strongly-typed language, you have to be aware of trying to stuff an incompatible data type into a token. It's been a few years but IIRC both C# and Python variables can accept NULL values by default. I've been away from it for about 7 years, so I'm rusty. But it's [I]really[/I] useful particularly in booleans where you can distinguish clearly between "Yes", "No" and "Don't know." I've seen programmers get themselves into very sticky corners by writing code that doesn't recognize NULL values. They design the DB (something most programmers don't have the training for) and don't allow NULL values on boolean fields, not wanting to deal with that additional complexity. Depending on the context, there can be a HUGE difference between "No" and "Don't know." IAC, this is just hobby-level development. I'm in no rush, so if I have to wait until I have a beefier machine to work with it's NBD. [/QUOTE]
Verification
Post reply
Forums
macOS & iOS Developer Playground
iOS Development
Xcode performance
Top