关于死锁的各种说法中正确的有(18)。为了预防死锁，我们会采取很多措施，其中采用资源一次性分配措施是为了破坏(19)条件。

 ①在互斥条件下，即某一段时间内某资源仅为一进程所占用时，有可能发生死锁

 ②在请求和保持条件下，即当进程因请求资源而阻塞，却对已获得的资源保持不放的情况下，有可能发生死锁

 ③在不剥夺条件下，即进程已获得的资源在未使用完之前不能被剥夺，而只能在使用完时由自己释放，有可能发生死锁

 ④在发生死锁时，必然存在一个进程——资源的环形链。

(77)

(76)

(78)

(75)

Tile　hardware　are　the　parts　of　computer　itself　including　the(71)(CPU)and　related　microchips　and　micro　-circuitry,　keyboards,　monitors,　case　and(72)(including　floppy,　hard,　CD,　DVD,　optical,　tape,　etc...).　Other　extra　parts　called(73)or　devices　include　mouse,　printers,(74),　scanners,　digital　cameras　and　cards(sound,　colour,　video)etc...　Together　they　are　often　referred　to　as　a(75)or　PCs.

(72)

(73)

(71)

(70)

C　is　sometimes　referred　to　as　a　'high　-level(66)language'.　Some　people　think　that's　an　insult,　but　it's　actually　a　deliberate　and　significant　aspect　of　the　language.　If　you　have(67)in　assembly　language,　youll　probably　find　C　very　natural　and　comfortable(although　if　you　continue　to　focus　too　heavily　on　machine　-　level　details,　youll　probably　end　up　with　unnecessarily　non-　portable　programs).　If　you　havent　programmed　in　assembly　language,　you　may　be　frustrated　by　C　's　lack　of　certain　higher　-　level　features.　In　either　case,　you　should　understand　why　C　was　de-　signed　this　way:　so　that　seemingly　-　simple　constructions　expressed　in　C　would　not　expand　to　arbitrarily　expensive(　in　time　or(68))machine　language　constructions　when(69).　If　you　write　a　C　program　simply　and　succinctly,　it　is　likely　to　result　in　a　succinct,　efficient　machine　language　executable.　If　you　find　that　the(70)resulting　from　a　C　program　is　not　efficient,　it's　probably　because　of　something　silly　you　did,　not　because　of　something　the　compiler　did　behind　your　back　which　you　have　no　control　over.　In　any　case,　there's　no　point　in　complaining　about　C's　low　-　level　flavor:　C　is　what　it　is.