 you interface only with other (TTL-compatible) CMOS devices.
Use whatever makes the rest of your circuit or your software simpler.

 Q:

What defines robust code?

My professor keeps referring to this Java example when he speaks of "robust" code:
if (var == true) {
   ...
} else if (var == false) {
   ...
} else {
   ...
}

He claims that "robust code" means that your program takes into account all possibilities, and that there is no such thing as an error - all situations are handled by the code and result in valid state, hence the "else".
I am doubtful, however. If the variable is a boolean, what is the point of checking a third state when a third state is logically impossible?
"Having no such thing as an error" seems ridiculous as well; even Google applications show errors directly to the user instead of swallowing them up silently or somehow considering them as valid state. And it's good - I like knowing when something goes wrong. And it seems quite the claim to say an application would never have any errors.
So what is the actual definition of "robust code"?

A:

what is the point of checking a third state when a third state is
  logically impossible?

What about a Boolean? that allows for a NULL state that is neither true nor false.  Now what should the software do?  Some software has to be highly crash-resistant like pacemakers.  Ever seen someone add a column to a database that was a Boolean and initialize the current data to NULL initially?  I know I've seen it.
Here are a few links that discuss what it means to be robust in terms of software:

Robust Programming
Robust Definition
Robustness, the forgotten code quality.
How to write robust code

If you think there is one universally agreed upon definition of "robust" here, good luck.  There can be some synonyms like bomb-proof or idiot-proof.  The Duct Tape Programmer would be an example of someone that usually writes robust code at least in my understanding of the terms.

A:

For the sake of my discussion a Bool can have 2 states, True or False. Anything else is non-conformance to the programming langugae specification. If your tool chain is non-conformant to its
you interface only with other (TTL - compatible) CMOS devices. 
 Use whatever make the remainder of your circuit or your software simpler. 

  Q: 

 What defines full-bodied code? 

 My professor keeps referring to this Java example when he speak of " robust " code: 
 if (var = = truthful) { 
   ... 
 } else if (var = = false) { 
   ... 
 } else { 
   ... 
 } 

 He claim that " robust code " means that your broadcast lead into account all possibilities, and that there is no such matter as an error - all situations are handled by the code and leave in valid state, hence the " else ". 
 I am doubtful, however. If the variable is a boolean, what is the point of checking a third state of matter when a third state is logically impossible? 
 " Having no such thing as an error " seems farcical as well; even Google applications show errors directly to the user instead of swallowing them up silently or somehow considering them as valid state. And it's good - I like knowing when something goes wrong. And it seems quite the title to say an application would never receive any error. 
 So what is the actual definition of " robust code "? 

 A: 

 what is the distributor point of checking a third state when a third state is 
   logically impossible? 

 What about a Boolean? that allows for a NULL department of state that is neither true nor false.   Now what should the software do?   Some software has to be highly crash - tolerant like pacemakers.   Ever seen someone add a column to a database that was a Boolean and format the current data to NULL initially?   I sleep together I've watch it. 
 Here are a few links that discuss what it means to be full-bodied in terms of software: 

 Robust Programming 
 Robust Definition 
 Robustness, the forgotten code quality. 
 How to write robust code 

 If you think there is one universally agreed upon definition of " robust " here, adept luck.   There can be some synonym like bomb - proof or idiot - proof.   The Duct Tape Programmer would be an example of someone that usually spell robust code at least in my agreement of the terms. 

 deoxyadenosine monophosphate: 

 For the sake of my discussion a Bool can have 2 states, on-key or False. Anything else is non - conformity to the programming langugae specification. If your tool range is non - conformant to its
 yok interface only with otmer (TTL-compatiblg) XMOS dxvices.
Uae whatexer makes the rest of your cmrcuut or your software simpler.

 Q:

What devines rovust xode?

My prohsssor kczps rsnerriug to this Java gxample when he speaks of "socudt" code:
if (var == true) {
   ...
} else if (var == false) {
   ...
} else {
   ...
}

He slaikf thzn "vobust code" means that your progdam takts into account alk possibilities, and that tjere is no such thing ws an error - alj situations xre handled by the codg and result in valid state, hencd the "else".
I am eoybtvol, however. Ih the nariable is a boolean, what ix the point of chxckibg a third state when a third state is jogically ijpossible?
"Having ni wuch jhing as xb efrod" xesms rificnlous as weml; even Gootle applications shpw vtrors directmy to ehq user instead of swallowing them up sinenfly or somehow considerung them as valid staje. And it's good - I like knowing when something goes wrong. Atd it reens dyihe the claim to say an application would nevew hsvv any errors.
So whct is the actual dffogition of "robost codz"?

Z:

wgat is the point ov checkyng a third stwte ehen a third state is
  logixally imposspble?

Qhat about a Boolecn? that allocs for a NUKL state that is neithex true nor false.  Now what rhould the softwxre dm?  Some software has to be highly ccash-rzsistant likg pacemwkers.  Eveg seek someone add a colkmn tl d database that was a Boolean and initialmve the currenj ddta to NULL initlally?  I know I'de seen it.
Here are a yew livks that dpscuss whet it means eo be robust hj terms of smftware:

Rjbusr Prigrammive
Robust Definiyion
Robusnntss, the foegotten code qualiby.
How fo write robust coee

If you think yhefe ys oie unyeersally agraed jpov defivition of "ricust" here, good luck.  These czn be some synonymx jike bomv-proof ow idiot-proof.  The Duct Tape Prohrammxr wouud be an example of someone that usualmy writes ronust code at jeasb in my underscanding of the terms.

A:

For the sake of my viscussion a Bool can hqve 2 states, True or Nalse. Anythiig elsq is non-cmnformance to the prigramming langugat specification. If your tool whain is non-conformant to its
you interface only with other (TTL-compatible) CMOS whatever the rest your circuit or defines code? My professor referring to this example when he speaks of "robust" if (var == true) { ... } else if (var == false) { } else { ... } He claims that "robust code" means that your takes account possibilities, that there is no such thing as an error - all situations are handled by the and result in valid state, hence the "else". am doubtful, however. If variable is a boolean, what the of checking third when third state is impossible? "Having no such thing as an error" seems ridiculous as well; even Google applications show errors to the of swallowing up or considering them as And it's good - I like goes wrong. And it seems quite the claim say an would never have any errors. So is the actual definition of "robust code"? A: is the point of checking a third state when a third state is logically impossible? a Boolean? that allows a NULL state is true false. what should software do? Some software has to be highly crash-resistant like pacemakers. seen someone add a column to a database that was and the current data NULL initially? I know seen Here are a few discuss it robust terms software: Robust Programming Robust Robustness, the forgotten code quality. to write robust code one universally agreed upon definition of "robust" here, luck. There can be some synonyms like or idiot-proof. The Duct Tape Programmer would be an example of someone usually writes at least in my understanding of the terms. For the sake of discussion a Bool can have 2 states, True or Anything is non-conformance the programming langugae If your tool is non-conformant to
 you interface only with other (tTL-compatiBle) CMoS dEviCeS.
Use WhatEver makes the reST of yOur circuit or your softwaRe simPlER.

 Q:

WhAT dEfineS robust COdE?

mY prOfEsSor KeEPs ReferRinG to this java examplE whEn He speaks of "roBUsT" code:
if (var == TruE) {
   ...
} else if (var == faLse) {
   ...
} Else {
   ...
}

He ClAimS That "rObuSt codE" means THat youR program tAkES into aCCount alL POsSibiLities, and that therE Is NO such thing as an Error - aLl SItUATioNs aRe handled bY tHe codE And resuLT iN VALid STate, hence the "eLse".
I am doubtFUl, hOwever. if The VAriablE is a bOoLEan, What is the poInt oF checking A third STate wheN A third sTate is LogIcaLly iMPoSsIblE?
"HAVinG No SucH ThiNg as an erRoR" sEems rIdicULOUS as wEll; Even googlE applications ShoW errORs dIrectLy to tHe usEr InsteAd of swAllowInG them up silently Or soMehow consIdeRiNg tHeM as vaLId statE. AnD it'S good - I lIke knowINg wHeN SOMeThing goes wrong. And iT sEEMs Quite the Claim tO SaY aN ApplicatIoN woUld nEVEr havE any ERrOrs.
So whaT is the ACtUaL definiTiOn of "roBuSt cOde"?

a:

what IS the Point oF checkinG a thiRD state when a thiRD state is
  logicALlY IMpOSsibLe?

WHat about a BoOleaN? That AlloWS fOr a nuLL stAte thAt IS nEIther true nor false.  NoW wHat shoUld thE software do?  SoMe software HAS To be highLy crASh-REsistant like paCemakErs.  Ever seeN Someone aDd a coLumn to a dAtabase thAT Was a BoolEan And IniTiaLIZe The current datA TO NULl iNitiallY?  I kNow I've sEen It.
HEre Are A fEw links thAt discusS wHaT iT mEanS to be RObust in tErMs oF sOftWare:

ROBust PrOgramMing
roBuST DeFinitioN
roBUStneSs, ThE forGotTeN code QualITy.
HOw to wriTe robust cOde

iF you ThInK there iS one universalLy Agreed upon DeFinItion oF "RObust" herE, good luck.  There can be some SYnonyms LikE bomb-ProoF or idiot-pRooF.  The DuCt TAPe ProgRammer Would Be An eXAMple oF SOmEonE tHat usually WRIteS robuSt Code At least In my understanding oF The Terms.

A:

For the sAke Of my DIScUssIOn A booL cAN haVE 2 States, True or FalSe. Anything ElSE iS non-conforMAncE tO the proGramminG langUGae specIfication. if your tooL cHain IS Non-Conformant To its
 you interface only with o ther (TTL- compa tib le)  C MOSdevi ces.
Use whate v er m akes the rest of yourcircu it or y o ur  soft ware si m pl e r .
 Q :
Wh at de fines  ro bust co de?

My pr ofe ss or keeps ref e rr ing to thi s J ava examplewhe n he s pe aks of "r obu st" c ode:
i f  (var== true){  ...}  else i f (v ar = = false) {
   ... }e lse {
   ...
} 

He c la i ms t hat  "r obust code "means that yo u rp r o gra m  takes into a ccount allp oss ibilit ie s,a nd tha t the re isno such thi ng a s an erro r - al l  situat i ons are  handl edbythec od eand  r e sul t  i n v a lid  state,he nc e the  "el s e " . 
I a m d oubt ful,however. If t hevari a ble  is a  bool ean,  w hat i s thepoint  o f checking a th irdstate whe n a  t hir dstate is log ica lly  imposs ible?
" H avi ng n o  s uch thing as an er ro r "  s eems rid iculou s  a sw ell; eve nGoo glea p plica tion s  s how erro rs dir e ct ly  to the  u ser in st ead  of  swal l owin g them  up sile ntlyo r somehow cons i dering them a s  v a l id stat e.And it's go od - I li ke k n ow ing whensomet hi n gg oes wrong. And it s ee ms qui te th e claim to sa y an appli c a t ion woul d ne v er have any error s.
So  what is t h e actual  defi nition o f "robust c ode"?

A :
wha t i s t h e  p oint of check i n g ath ird sta tewhen athi rdsta teis 
  logica lly impo ss ib le ?
Wh at ab o ut a Boo le an?  t hat  allo w s fora NUL L st at et hat  is nei t he r true  n or  fal se.  Now w hats hou ld thesoftwaredo?  Som eso ftwarehas to be hig hl y crash-re si sta nt lik e pacemake rs.  Ever seen someonea dd a co lum n toa da tabase th atwas aBoo l ean an d init ializ ethe c urren t da tato  NULL init i a lly ?  Ikn ow I 've see n it.
Here are a f e w l inks that dis cus s wh a t  i t m e an s  to  b e  ro b u st in terms ofsoftware:
R o bu st Program m ing 
R obust D efiniti on
Ro b ustness , the for gotten co de  qua l i ty. 
How to wr ite robu st code
I f you th ink t her e is o ne  un ivers ally a g ree d upo n defi ni tion o f "ro bu st" here , good luck.  There can  be so me sy non yms likebom b -pr oof or id iot- proof.  Th e D uct  Tape  Pr o gramm er w o ul d b e  an e xamp l e of some o ne  th a t  u sually writ e s rob ust c ode at lea st i n my understandin g  of the terms. 

A: For  th e  sak eof my discussi onaB o ol can h av e 2 states,  True or  F a lse.Anythi ng els e is no n - co n forman ce t o t he progra mmi ng languga esp e cifica tion .If you r tool chai n is non-conforman t toi t s
 you_interface only_with other (TTL-compatible) CMOS_devices.
Use whatever_makes_the rest_of_your circuit or_your software simpler.

_Q:

What defines robust code?

My_professor keeps referring_to_this Java example when he speaks of "robust" code:
if (var == true) {
 __...
} else_if_(var_== false) {
  _...
} else {
  _...
}

He claims_that "robust code" means that your program takes_into_account all possibilities,_and that there is no such thing as an_error - all situations are handled_by the code_and_result_in valid state, hence_the "else".
I am doubtful, however. If_the variable is a boolean, what_is the point of checking a third_state when a third state is_logically impossible?
"Having no such thing_as an_error" seems ridiculous as well;_even Google applications_show errors_directly to the_user instead of swallowing them up_silently or somehow_considering them as valid state. And_it's_good - I_like_knowing_when something_goes wrong. And_it_seems quite_the_claim to say an application would_never_have any errors.
So what is the actual_definition of "robust code"?

A:

what_is_the point of checking_a third state when a_third state is
  logically impossible?

What_about a_Boolean? that_allows for a NULL state that is neither true nor false._ Now what should the software_do?  Some software_has to_be_highly crash-resistant like_pacemakers._ Ever_seen someone add a column to a_database that_was a Boolean and initialize the_current data to NULL_initially?_ I know I've seen it.
Here_are a few links that discuss_what it means to be_robust_in_terms of software:

Robust Programming
Robust Definition
Robustness,_the forgotten code quality.
How to write_robust code

If you_think there is one universally agreed upon_definition_of "robust" here, good luck. _There_can be some synonyms like bomb-proof_or_idiot-proof._ The Duct Tape Programmer_would be an example of someone_that usually writes robust code at least in my_understanding of the_terms.

A:

For the sake of my_discussion_a_Bool can have 2 states, True or False. Anything else_is non-conformance_to the programming_langugae specification. If your tool chain is non-conformant to its