「d dur」を含む日記

はてなキーワード:d durとは

2024-03-26

■米津玄師がLemonのPVでヒールの靴を履いている理由

Everyone been wonder ing why Yonezu (last name) Kenshi (firstname)is wearing the heeledshoes. Inone ofhis interviews he said thatonce hedreamed afun eral. Everyone was sad, but suddenlysomeone in the firstline started towhistle loudly, in a way that annoyed the other people. Theyall started to say that hewasn't respecting the dead person because hewasn'tbeing in silence forhim, but Kenshi knew that theman whistling was communicating with the deadone. Thatwas their own unique way to recognize each other.Maybe the otherswill thinkyou'recrazy orsomething negative, butit won'tchange the love that the whistling man has forhis deadfriend. Turnsout that Kenshigot inspiredby this dream so in the sing he wore heeledshoes, because hewants to let us know that he doesn't care what others say,it'shis special way toexpress himself, because Kenshiwas affectedby High-function ing Autism which broughthim to be smarter than the aver age, but he couldn't handle with social relationships, that'swhy he never hadmanyfriends since ayoungage and everyone made fun ofhim because ofhis character.

米津（姓）ケンシ（名）がなぜヒールの靴を履いているのか、誰もが不思議に思っていることだろう。

彼はあるインタビューで、葬式の夢を見たことがあると言っていた。みんな悲しんでいたのに、突然一列目の誰かが、他の人たちを困らせるような大きな口笛を吹き始めた。

彼らは皆、口笛を吹いているのは死者に敬意を払っていない、死者のために黙っているのではない、と言い始めた。それが彼ら独自の認識方法だったのだ。

もしかしたら、他の人からは頭がおかしいとか否定的な見方をされるかもしれないが、口笛を吹いている男が死んだ友人を愛していることに変わりはない。

というのも、ケンシは高機能自閉症の影響を受けていて、平均よりも頭がいいのだが、社会的な人間関係をうまくこなすことができなかった。

This made Kenshi very sad and from thenon hestarted tohate himself because ofhis very uncommon name (inJapan there aren'tmany people that have Yonezuas last name and noone, but Yonezu Kenshi,is called Kenshi or the spell ing is similar, plusit soundslike a stage name as well) he thought hewas strange andweird, an uncommon person who shouldn't have existed (infact inJapan thereis a very strongwill to follow the mass, which means ifthe great er part of girls have bangs, then the girls without bangswill try to have them or if they remain what they are, they might beisolated because different from therest of the population). But Kenshi tomake us,his fans, satisfied, he decided to collaborate withmany people in the 2017like the animators for MHA,DAOKO and SudaMasaki.

このことがケンシをとても悲しくさせ、それ以来ケンシは自分の名前の珍しさ（日本では米津を名字に持つ人は少ないし、米津ケンシ以外はケンシと呼ばないし、スペルも似ていない、存在しないはずの珍しい人（実際、日本では大衆に従おうとする意志が非常に強い。つまり、前髪のある女の子が多ければ、前髪のない女の子も前髪を作ろうとするし、前髪のないままだと、他の人とは違うという理由で孤立するかもしれない）。しかし、ケンシは私たちファンを満足させるために、MHAのアニメーターやDAOKO、菅田将暉など、2017年に活躍した多くの人々とのコラボレーションを決めた。

Hechange d dur ing his musical career,like the time hewas still Hachi (ハチ) and hefelt somehowlost inall ofhis fame, so hemade this song wearing heeledshoes and then thenext song, Flamingo,is very different from Lemon becausemany peoplestarted to listen and to knowhim after Lemon, but he wanted to know what they would think if Kenshichanged the rhythm and the kind, turnsout thatmany of them were attractedby Lemon and they didn'tlike Flamingo, but theystill subbed to Kenshi'sYouTube channel. Thankyou for reading all of this,English isn't mymother language so I'msorry for the mistakesand asalways, have a nice day :D

彼は音楽活動の中で変わっていった。例えば、彼がまだハチだった頃、有名になることにどこか迷いを感じて、ヒールのある靴を履いてこの曲を作った、というのも、多くの人がLemonの後にKenshiを聴き始め、知るようになったからだ。しかし、彼はKenshiがリズムや種類を変えたらどう思うかを知りたかった。英語は母国語ではないので、間違いがあってごめんなさい。

Edit:You can find a videosummary of Yonezu Kenshi'slife and a ll ofhis interviews,it's inMandarin tho. Ihope you have a good translator to understand what he's saying.

米津建志の人生とインタビューの要約ビデオを見ることができます。彼が何を言っているのか理解するために、良い翻訳者がいることを願う。

Permalink |記事への反応(0) | 06:44

ツイートシェア

2023-11-15

■Dehradun Call Girls | skokkacallgirl

Areyou tired of searching all around Dehradun for attractiveand a lluring call girls? If so,you've come to the correct place. We provide the besthotel Dehradun Call Girls. Our housewives are attractive and beautiful. They'll enhanceyour day with evenmore unique touches. Therefore, ifyou'dlike to spendtime withsomeone who is so beautiful,you should employ our services.You can reserve our Dehradun call women wheneveryou want, from anywhere. Utilis ing our servicesis quite easy. To submit the form, simply fill it out and emailit to theaddress provided. After submitting the form, anSMS containing a confirmationlink will be sent toyou.

Onceyou've clicked this link, complete the payment.Your booking infowill be sent toyourmobile device in a matter of minutes. Greetings from Skokka Call Girls, from Dehradun call girls. Strong bondsbetween couples are forged dur ing meaningful and enjoyablesex encounters, which also help peopletransition smoothly throughlife. However, we want to eliminate stressful marriages, arguments about not having enoughtime forone another, pressure from theworkplace orauthority, and relationships that are under duress in this new setting. Relationship stressis causing men's personal lives to deteriorate daily. Thesedays, finding a partner that fitsyourneeds, tastes, and personalityis challenging.

Very few people nowadays are lucky enough to have a thoughtful, kind, and compatible companion. Peoplewho are unhappy anddon'tvalue relationships are theones looking forindependent Dehradun call girls. Every one is capable of andhas an innate yearning forhappy, fulfill ing sexual experiences; they are not entitled to alife filledwith tension, hopelessness,and a lack oflove andpleasure.

Call Girls Chandigarh

Call Girls Amritsar

Call Girls Agra

Call Girls Ahmedabad

Call Girls Ajmer

Call Girls Ambala

Call Girls Aerocity

Call Girls Bangalore

Call Girls Chennai

Call Girls Coimbatore

Call Girls Delhi

Call Girls Dwarka

Call Girls Dehradun

Call GirlsGoa

Call Girls Guwahati

Call Girls Gurgaon

Call Girls Ghaziabad

Call Girls Haridwar

Call Girls Hyderabad

Call Girls Faridabad

Call Girls Indore

Call Girls Jalandhar

Call Girls Jaipur

Call Girls Jaisalmer

Call Girls Jodhpur

Call Girls Kolkata

Call Girls Kharar

Call Girls Ludhiana

Call Girls Lucknow

Call Girls Mumbai

Call Girls Manali

Call Girls Mussoorie

Call Girls Mahipalpur

Call Girls Mohali

Call Girls Mysore

Call Girls Noida

Call Girls Nagpur

Call Girls Panchkula

Call Girls Patiala

Call Girls Patna

Call Girls Pune

Call Girls Rishikesh

Call Girls Rohini

Call Girls Surat

Call Girls Udaipur

Call Girls Varanasi

Call Girls Vadodara

Call Girls Zirakpur

backlink

Permalink |記事への反応(0) | 03:21

ツイートシェア

2023-10-20

■

Refuting the “Israeli” Claims Regarding Evading their responsibility for the Massacre of the Gaza Baptist Hospital

Today, the “Israeli” Occupation Entityis try ing to evade their responsibility for the crime ofbombarding the “Baptist” ArabNational Hospital in GazaCity, which theIsraeli” Occupation Forces (IOF) committedon the evening of Tuesday,17 October 2023. This heinous crimewas committed against innocentPalestinian civilians while taking the hospitalas a shelter from theflames of the “Israeli” brutal aggression, which leftnowhere safe in the besieged enclave.It is necessary to affirm that, the Baptist Hospital belongs to the Anglican Episcopal Church in Jerusalem, andwas built beforethe occupation ofPalestine.

It is obvious that the “Israeli” enemyhas been spreading lies since the very beginning ofhis destructivewar on our people, when he with no singleevidence claimed that thePalestinian resistance killed children, cut offheads and raped women. In continuation of this series of lies, they tried to evade their crime,attributing it toone of theresistance factions. Accordingly, we present some of the conclusiveevidence to prove the “Israeli” Occupation Entity responsible for this heinous crime:

1)It is nosecret that the IOF, severaldays ago, threatened several hospitals in the Gaza Strip, contacting each hospital separately and requesting their evacuation and holding the hospitalsdirectors responsible for the consequences of neglecting the threats. Infact, there are dozens of clearstatements from the IOF spokespersons in this regard.

2) Since thebeginning of theongoing aggression, the “Israeli” armyhas ignored the principle of distinguishing between civilian and military targets. Thus, thebombardmenthas systematically targetedemergency services, ambulances, civil defense facilities, schools, mosques, and churches.

3) The IOF contacted thedirectors of 21 hospitals in the Gaza Strip, especially those are located in the Gaza and the North of Gaza governorates,most notably: (Al-Awda, the Indonesian, Kamal Adwan, the Kuwaiti, Al-Quds,and Al-Mamadani),asking them to evacuate immediately, given that the hospitals are located within the geographicalscope of “Israeli” military operations. In this regard, theofficial spokespersons for the IOF plus anumber of hospitaldirectors conducted interviewslive on Al Jazeera, revealing the premedit ated intention of the IOF to target hospitals in the Gaza Strip.

4)On 14October,2023,at 20:30, the IOFfiredtwo shells towards the Baptist Hospital, and thenext morning they called the hospitaldirector, Dr. Maher الصفحة 2 من 3

Ayyad, saying tohim: “Wewarnedyou last evening with two shells, sowhy haveyou not evacuated the hospital until this moment?!” Following that call, The hospitaldirector contacted the bishop of the Evangelical Church inBritain and informedhim of the incident,who in turn contactedinternational organizations before sending the hospital amessage reassuring them that they could remain in the hospital. Yet withno warning, the IOF airstrikes returned,on Tuesday evening, to carryout the massacre against the hospital and the shelter-seekers of the displaced innocentPalestinian civilians.

5) Immediately after the massacre, the IOF spokesperson quickly published astatement on his pageon the “X” and “Telegram” platformsat 21:17, which stated, “We hadwarned the evacuation of the Baptist Hospital andfive other hospitals so that theHamas terroristorganization would nottake as a safehaven”. That statement is a clear claim of this massacre, andit is documented with a “screenshot”image attached tohis pageon Telegram, but he quickly deleted the post after seeing the massivescale of the massacre for the largenumber of victims, and the angryresponses of the Arab, regional andinternational communities. Lateron, he disavowedit, publishanother

statement denying that he hadissued the firststatement.

6) Before and dur ing the event, theresistance factionsdid notfire any missilesat the occupied territories, the “Israeli” sirensdid not activate, and the Iron Dome missiles were not launched.Moreover, dozens of reconnaissance drones do not leave thesky of the Gaza Strip (365 km2 ), photographing and mon itoring every inch around the clock. If the massacrewas due to theresistance’s missiles,as the “Israeli” Occupation Entity falsely claim,why would not they showone picture their claims?!

7) The “Israeli” Occupation Entity claimed that this massacrewas causedby a missile launchedby theIslamic Jihad. However, we would wonder how they could identify and distinguishbetween the missiles of theresistance factions immediately after they were launched?!

8) The IOF military system documents and recordsall their operationsby day, hour, minute and second, and inall previous times their mediaoutlets cameout to announce or deny much less severe massacres than this massacre,so what made them wait more than 4 hours before declaring their irresponsibility other than weaving scenarios of falsification, lies and deception?!

9)It is obviously known that theresistance’s missiles are somewhat “primitive” and do not have the destructivepower that kills hundredsat onetime. And throughout thehistory of previous confrontations and the current confrontation, noresistance missilehas caused a tenth of this number of “Israeli” deaths.

10) Theonly video scene documenting themoment ofthe explosion reveals that the mass offlame and the sound ofthe explosion are identical to other “Israeli”bombs throughout thedays of theongoing aggression, which withno doubt proves that the “Israeli”origin of the missile.

الصفحة 3 من 3

The deliberateattackon hospitalsis awar crime, stipulated in Article (8, 2, b, 9) of the Statute of theInternational Criminal Court. Accordingly,Hamas officially callson the Prosecutor of theInternational Criminal Court toopen an investigation into this crime, which falls within theframework of a genocidalwar, in accordancewith the provisions of Article 6 of theBasic Law. Thesebloody acts are also basedon the policy of denial pursuedby the “Israeli” Occupation Entity,as they denythe ex istence of thePalestinian people.

Thereis no doubt that impunity fuels crime, and investigat ing crimesis a way to protect people. Furthermore, if a legal and judicialresponse is necessary,it is aboveall that theresponse to this crime must be humanitarian and global. Such actions mustshock the conscience ofthe world, or else there would no longer be a reliableinternational community if the “Israeli” Occupation government free to decide tobomb hospitals!

In conclusion, we are facing a genocidal massacre committedby IOF against children, women, and the elderly. The “Israeli” Occupation Entityis theonly responsible for the crime, no matter how much theytry to weave lies and fabrications toget away withit,as theyalways do.

TheIslamicResistance Movement

HAMAS-Palestine

Wednesday, 18October 2023

本日ハマスがpdf 形式でテレグラムにアップしたやつの全文

「ガザ・バプテスト病院虐殺の責任回避に関するイスラエルの主張に反論する」

って題名

Permalink |記事への反応(1) | 21:27

ツイートシェア

2023-02-19

■打上げ 成功/失敗のWikipedia的定義

https://en.wikipedia.org/wiki/Comparison_of_orbital_launcher_families

Launchesreach ing...
Total: Flights whichlift-off, or where the vehicleis destroyed dur ing the terminal count
Note:only includesorbital launches (flights launchedwith the intention ofreach ing orbit). Suborbital tests launches are not included in this listing.
Space (regardless of outcome): Flights whichreach approximately 100km ormore aboveEarth's surface.
Any orbit (regardless of outcome): Flights which achieveat leastone completeorbit even ifthe orb it differs from the targetedorbit.
Targetorbit (withoutdamage to the payload)

この部分が、成功率を比較するための項目と言って良いと思う。成功率そのものはこの記事では述べていないが

成功率="Targetorbit"÷"Total"

と見ればよい。

で、Totalの定義としては、「離陸するか、または最終カウントダウン中に破壊された数」。なお、衛星軌道への打ち上げのみをカウントし、弾道飛行テストはカウントしない。

H3は今回、離陸も破壊もしなかったので、Totalは0のまま。

Permalink |記事への反応(1) | 22:44

ツイートシェア

2021-01-06

■anond:20210106141407

アジア圏では反社の証明なので・・・で終わるし

反社の証明じゃないもんな国でもこんなモンだが？

　
タトゥーだって元軍人とかならばともかくそれ以外は教会で悪口を言われた云々とかやってるし
クラブとか海ならなんも言わんだろうけどそれ以外は場所とシチュエーション次第なんだが？
Tattoos, Piercings, and Credibility
Of the nearly 2,700 people we surveyed,12% reported having a visibletattoo that can be seenby managers and co-workers during the workday.Only 3% reported having a visiblebody piercing (other than an earring).
The biggest takeaways from our survey include a whopping 76% of respondentsfeel tattoos and piercings hurt an applicant’s chances ofbeing hired dur ing a jobinterview. Andmore thanone-third – 39% of those surveyed –believe employeeswith t attoos and piercings reflect poorlyon their employers. Furthermore, 42%feel visibletattoos arealways inappropriateat work, with 55% reporting the same thing aboutbody piercings.
Fortunately,only 4% of thosewith t attoos and piercings report having faced actual discrimination because of theirink andbody art.
　
刺青・ピアス・信用度
調査対象となった約2,700人のうち、12%の人が、勤務中に上司や同僚に見られるようなタトゥーを入れていると報告しています。
ピアス（イヤリング以外）をつけていると答えたのはわずか3%でした。
調査から得られた最大の収穫は、回答者の76%が、タトゥーやピアスが面接採用に悪影響を与える可能性を感じているとのことです。
また、3分の1以上（調査対象者の39％）が、タトゥーやピアスをしている従業員は、雇用主に悪い印象を与えると考えています。
さらに、42%は、目に見えるタトゥーは常に職場では不適切だと感じており、55%はボディピアスについても同様のことを報告しています。
幸いなことに、タトゥーやピアスをしている人のうち、インクやボディアートが原因で実際に差別に直面したことがあると報告しているのは、
わずか4%に過ぎません。
　
Tattoos Hurt Your Chances of Getting a Job
https://www.salary.com/articles/tattoos-hurt-chances-getting-job/
　
なお上記はカンザス州の企業。でも保守的な地域でなくともドレスコードで見えるところは禁止ってやってるとこ少なくないよ
最近は緩和されてきたみたいだが
ヨーロッパも同じ印象というか更に保守的なイメージあるけどな
　

Permalink |記事への反応(0) | 14:17

ツイートシェア

2020-10-22

■anond:20201022143258 anond:20201103113726

海外は日本以上にTPOと異装に厳しぞ

タトゥーだって元軍人とかならばともかくそれ以外は教会で悪口を言われた云々とかやってるし

クラブとか海ならなんも言わんだろうけどそれ以外は場所とシチュエーション次第なんだが？

Tattoos, Piercings, and Credibility
Of the nearly 2,700 people we surveyed,12% reported having a visibletattoo that can be seenby managers and co-workers during the workday.Only 3% reported having a visiblebody piercing (other than an earring).
The biggest takeaways from our survey include a whopping 76% of respondentsfeel tattoos and piercings hurt an applicant’s chances ofbeing hired dur ing a jobinterview. Andmore thanone-third – 39% of those surveyed –believe employeeswith t attoos and piercings reflect poorlyon their employers. Furthermore, 42%feel visibletattoos arealways inappropriateat work, with 55% reporting the same thing aboutbody piercings.
Fortunately,only 4% of thosewith t attoos and piercings report having faced actual discrimination because of theirink andbody art.
　
刺青・ピアス・信用度
調査対象となった約2,700人のうち、12%の人が、勤務中に上司や同僚に見られるようなタトゥーを入れていると報告しています。
ピアス（イヤリング以外）をつけていると答えたのはわずか3%でした。
調査から得られた最大の収穫は、回答者の76%が、タトゥーやピアスが面接採用に悪影響を与える可能性を感じているとのことです。
また、3分の1以上（調査対象者の39％）が、タトゥーやピアスをしている従業員は、雇用主に悪い印象を与えると考えています。
さらに、42%は、目に見えるタトゥーは常に職場では不適切だと感じており、55%はボディピアスについても同様のことを報告しています。
幸いなことに、タトゥーやピアスをしている人のうち、インクやボディアートが原因で実際に差別に直面したことがあると報告しているのは、
わずか4%に過ぎません。
　
Tattoos Hurt Your Chances of Getting a Job
https://www.salary.com/articles/tattoos-hurt-chances-getting-job/

なお上記はカンザス州の企業。でも保守的な地域でなくともドレスコードで見えるところは禁止ってやってるとこ少なくないよ

最近は緩和されてきたみたいだが

ヨーロッパも同じ印象というか更に保守的なイメージあるけどな

Permalink |記事への反応(3) | 15:02

ツイートシェア

2020-05-20

■翻訳 サービス 比較

原文

The TokugawaShogun atewas establishedby Tokugawa Ieyasu aftervictory at the Battle of Sekigahara, ending the civilwars of the Sengoku period following the collapse of the AshikagaShogun ate. Ieyasu became theShōgun and the Tokugawa clan governedJapan from Edo Castle in the easterncity of Edo (Tokyo) alongwith the daimyō lords of thesamurai class. The TokugawaShogun ate organizedJapanesesociety under the strict Tokugawa class system and bannedmost foreigners under the isolationist policies of Sakoku to promote political stability. The Tokugawa and daimyō de facto administeredJapan through their system of han (feudal domains) alongside the de jure Imperial provinces. The TokugawaShogun atesaw rapid economicgrowth and urbanization inJapan whichled to therise of the merchant class and Ukiyo culture. The TokugawaShogun ate declined dur ing the Bakumatsu ("Opening ofJapan") period from 1853 andwas overthrownby supporters of the Imperial Court in theMeiji Restoration in 1868. TheEmpire of Japan was established under theMeiji government and Tokugawa loyalists continued tofight in the BoshinWar until the defeat of the Republic of Ezoat the Battle of Hakodate inJune 1869.

Google翻訳

徳川幕府は、関ヶ原の戦いでの勝利後に徳川家康によって設立され、足利幕府の崩壊に続く戦国時代の内戦を終わらせました。家康は将軍になり、徳川藩は江戸の東の都市（東京）にある江戸城から武士の大名の領主とともに日本を統治しました。徳川幕府は厳格な徳川階級制度の下で日本社会を組織し、政治的安定を促進するために、サコクの孤立主義政策の下でほとんどの外国人を禁止しました。徳川と大明の事実上、日本は、ジュール帝国の領土とともに、藩（藩）のシステムを通じて管理されました。徳川幕府は、日本の急速な経済成長と都市化を見て、商人階級と浮世文化の台頭をもたらしました。幕末には幕末に幕を下ろし、明治維新により皇室の支持者たちにより打倒されました。明治政府のもと日本帝国が樹立され、徳川忠誠は1869年 6月の函館の戦いでのエゾ共和国の敗北までのぼしん戦争。

Excite 翻訳

徳川幕府は関ヶ原の戦いで勝利の後に徳川家康により設立されて、足利幕府の崩壊に続いている戦国時代の内戦を終えた。家康は、サムライクラスのdaimyō君主とともに江戸（東京）の東の都市の江戸城から Shōgunと徳川一族管理日本になった。徳川幕府は、厳密な徳川クラスシステムの下の日本の社会を組織し、政治的な安定性を促進するために、Sakokuの孤立主義者方針の下のほとんどの外国人を禁止した。徳川とdaimyō事実上は、正当な帝国地方のそばのhan（封建制度のドメイン）のそれらのシステムを通して日本を管理した。徳川幕府は、マーチャントのクラスとUkiyo文化の上昇に通じていた日本の急速な経済成長と都市化を見た。徳川幕府は、Bakumatsu（「日本の冒頭」）期間の間に1853から傾き、1868年に明治維新の宮中のサポーターにより倒された。大日本帝国は、1869年 6月に忠臣が函館戦争でエゾウの共和国の失敗までボシン戦争において戦い続けた明治政府と徳川の下で設立された。

DeepL翻訳

徳川幕府は、足利幕府の崩壊に伴う戦国時代の内乱を終結させ、関ヶ原の戦いで勝利した徳川家康によって成立しました。家康は将軍となり、徳川家は江戸城を拠点に武家の大名とともに日本を統治しました。徳川幕府は、厳格な徳川階級制度の下で日本社会を組織し、佐国の鎖国政策の下で外国人の入国を禁止して政治の安定を図りました。徳川と大名は、事実上の日本の行政を、事実上の皇国と並んで藩制度で行っていた。徳川幕府は急速な経済成長と都市化を遂げ、商人階級や浮世文化の台頭をもたらしました。徳川幕府は1853年からの幕末開国の時代に衰退し、1868年の明治維新で朝廷の支持者によって倒されました。明治政府の下で大日本帝国が樹立され、戊辰戦争では、1869年 6月の函館の戦いで蝦夷共和国が敗北するまで徳川家臣たちが戦い続けました。

みらい翻訳

関ヶ原の戦いに勝利した徳川家康によって徳川幕府が成立し、足利幕府の崩壊に伴う戦国時代の内乱は終結した。家康は将軍となり、徳川氏は武家の大名とともに江戸 (東京)東部の江戸城から日本を治めた。徳川幕府は、政治の安定を図るため、厳格な徳川階級の下で日本社会を組織し、鎖国政策の下ではほとんどの外国人を禁止しました。徳川と事実上の大名は、日本を藩制(藩)で実質的に支配した。日本は徳川幕府による高度経済成長と都市化が進み、町人階級や浮世文化が興った。1853年からの幕末(「日本の開国」)の間に徳川幕府は衰退し、1868年の明治維新で勤皇志士たちによって倒され、明治政府のもとに大日本帝国が成立し、1869年 6月の箱館戦争で蝦夷共和国が敗れるまで戊辰戦争を戦った。

Permalink |記事への反応(0) | 10:29

ツイートシェア

2020-03-26

■attracting commerce. Conditionson theisland improved dur ing the Taiping Rebellion in the 1850s, when manyChinese refugees, including wealthy merchants, fled mainland turbulence and settled in the colony.[16] Further tensionsbetween theBritish and Qing over the opium trade escalated into

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007743759-26-03-2020-Патриот-11-серия-канал-ТНТ-все-серии-сезона-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/en/community/posts/360007743959--Отречение-25-серия-украина-ТРК-26-03-2020-в-хорошем-качестве-

https://youtubecomhelp.zendesk.com/hc/en/community/posts/360007744939--В-шаге-от-рая-17-серия-Россия-1-26-03-2020-качество-HD-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/ru/community/posts/360007745060-26-03-2020-В-шаге-от-рая-17-серия-Россия-1-качество-HD-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/ru/community/posts/360007745040--Заступники-5-серия-26-03-2020-смотреть-бесплатно-в-хорошем-качестве-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/ru/community/posts/360007744019--Жизнь-после-жизни-10-серия-26-03-2020-последние-серии-смотреть-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/ru/community/posts/360007745940-26-03-2020-Корни-12-серия-СТС-все-серии-сезона-от-26-марта

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007744920-26-03-2020-Заступники-4-серия-последние-серии-смотреть-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007745960-26-03-2020-В-шаге-от-рая-13-серия-Россия-1-все-серии-сезона-

Permalink |記事への反応(0) | 20:10

ツイートシェア

■ngkong until 1926, when the government officially adopted thetwo-word name.[40] Some corporations founded dur ing the early colonial erastill keep thisname, including HongkongLand, Hongkong Electric Company, Hongkong andShanghai Hotels and the Hongkong andShanghai Banking Corporation (HSBC).[41][42]History

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007744139-26-03-2020-Последний-герой-Зрители-против-звезд-2-сезон-8-серия-все-серии-сезона-

https://youtubecomhelp.zendesk.com/hc/ru/community/posts/360007743779-26-03-2020-Отречение-21-серия-украина-ТРК-смотреть-в-хорошем-качестве-от-26-марта

https://youtubecomhelp.zendesk.com/hc/ru/community/posts/360007743859-26-03-2020-Любовь-на-выживание-9-серия-канал-пятница-смотреть-качество-HD-от-26-марта

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007744980--Заступники-3-серия-26-03-2020-качество-HD-

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007745200-26-03-2020-Холостяк-7-сезон-5-серия-тнт-смотреть-в-хорошем-качестве-

https://youtubecomhelp.zendesk.com/hc/pl/community/posts/360007744779-26-03-2020-Проспект-обороны-13-серия-на-канале-НТВ-смотреть-в-хорошем-качестве-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/en/community/posts/360007743719-26-03-2020-Корни-13-серия-стс-в-хорошем-качестве-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/en/community/posts/360007744959--Проспект-обороны-11-серия-НТВ-26-03-2020-онлайн-сериал-смотреть-от-26-марта-

https://youtubecomhelp.zendesk.com/hc/en/community/posts/360007746460--Доктор-Вера-13-серия-26-03-2020-смотреть-онлайн-в-хорошем-качестве-от-26-марта-

Permalink |記事への反応(0) | 20:07

ツイートシェア

2018-05-25

■anond:20180525141754

これやな

"I have spoken to SouthKorea andJapan and they are notonly ready should foolish or reckless acts betaken by NorthKorea, but they are willing to shoulder much of the cost ofany financial burden —any of the costs associatedby the United States in operations, if such an unfortunate situationis forced upon us," he said dur ing an eventat which he signed a bill rolling back bank regulations.

「韓国・日本との話はついてる。北朝鮮がアホで無謀な行動をとった場合の準備ができているって言ってるし、それだけじゃなくて、カネの面でも負担する用意があると言ってる。もしもそういった不幸な事態が避けられない場合、合衆国の作戦行動に関連する費用の一切をもつって」

そんなん知らんがな。

Permalink |記事への反応(0) | 14:37

ツイートシェア

2017-02-03

■clang:warning: argument unused during compilation: '-export-dynamic'

久しぶりにvimの更新したらこんなエラーが出たけどなんだこれ

Permalink |記事への反応(0) | 11:10

ツイートシェア

2016-10-17

■vimをtinyでmakeするとエラーが大量に出るんだが

インストール出来てるし起動もできてるから無視していいのかな

clang:warning: argument unused during compilation: '-I .'

clang:warning: argument unused during compilation: '-I proto'

clang:warning: argument unused during compilation: '-U _FORTIFY_SOURCE'

screen.c:1513:17:warning: self-comparisonalways evaluates totrue [-Wtautological-compare]

if (curwin == curwin)

screen.c:5676:19:warning: self-comparisonalways evaluates totrue [-Wtautological-compare]

&& Columns == Columns)

regexp.c:3790:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:3790:24:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:3790:24:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

regexp.c:4052:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:4052:24:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:4052:24:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

regexp.c:5276:25:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:5276:25:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:5276:25:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

regexp.c:5337:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

{ if ((rex.reg_match == ((void*)0))) *(&rex.reg_startpos[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.pos; else *(&rex.reg_startp[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.ptr; };

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:5337:24:note: remove extraneous parentheses around the comparison to silence thiswarning

{ if ((rex.reg_match == ((void*)0))) *(&rex.reg_startpos[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.pos; else *(&rex.reg_startp[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.ptr; };

~ ^ ~

regexp.c:5337:24:note: use '=' to turn this equality comparison into an assignment

{ if ((rex.reg_match == ((void*)0))) *(&rex.reg_startpos[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.pos; else *(&rex.reg_startp[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.ptr; };

regexp.c:5355:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

{ if ((rex.reg_match == ((void*)0))) *(&rex.reg_endpos[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.pos; else *(&rex.reg_endp[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.ptr; };

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:5355:24:note: remove extraneous parentheses around the comparison to silence thiswarning

{ if ((rex.reg_match == ((void*)0))) *(&rex.reg_endpos[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.pos; else *(&rex.reg_endp[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.ptr; };

~ ^ ~

regexp.c:5355:24:note: use '=' to turn this equality comparison into an assignment

{ if ((rex.reg_match == ((void*)0))) *(&rex.reg_endpos[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.pos; else *(&rex.reg_endp[rp->rs_no]) = (&rp->rs_un.sesave)->se_u.ptr; };

regexp.c:5516:22:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:5516:22:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:5516:22:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

regexp.c:6213:21:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:6213:21:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:6213:21:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

regexp.c:6266:25:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:6266:25:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:6266:25:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

regexp.c:6294:25:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:6294:25:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:6294:25:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

regexp.c:6325:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:6325:24:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:6325:24:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

regexp.c:6341:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:6341:24:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:6341:24:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

regexp.c:6363:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:6363:24:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:6363:24:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

regexp.c:7711:25:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:7711:25:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:7711:25:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

regexp.c:7740:23:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

regexp.c:7740:23:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

regexp.c:7740:23:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

In file included fromregexp.c:8043:

./regexp_nfa.c:3995:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:3995:24:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:3995:24:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:4014:21:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4014:21:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4014:21:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:4036:21:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4036:21:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4036:21:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:4055:21:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4055:21:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4055:21:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:4086:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4086:24:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4086:24:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:4227:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4227:24:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4227:24:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:4609:25:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4609:25:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4609:25:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:4670:22:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4670:22:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4670:22:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:4733:25:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4733:25:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4733:25:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:4767:25:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4767:25:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4767:25:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:4954:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:4954:24:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:4954:24:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:5106:21:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5106:21:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5106:21:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:5120:21:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5120:21:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5120:21:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:5144:25:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5144:25:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5144:25:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:5231:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5231:24:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5231:24:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:5486:25:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5486:25:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5486:25:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:5608:21:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5608:21:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5608:21:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:5897:23:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5897:23:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5897:23:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:5987:26:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:5987:26:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:5987:26:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:6873:26:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:6873:26:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:6873:26:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:6997:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:6997:24:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:6997:24:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

./regexp_nfa.c:7095:24:warning: equality comparison with extraneous parentheses [-Wparentheses-equality]

if ((rex.reg_match == ((void*)0)))

~~~~~~~~~~~~~~^~~~~~~~~~~~~

./regexp_nfa.c:7095:24:note: remove extraneous parentheses around the comparison to silence thiswarning

if ((rex.reg_match == ((void*)0)))

~ ^ ~

./regexp_nfa.c:7095:24:note: use '=' to turn this equality comparison into an assignment

if ((rex.reg_match == ((void*)0)))

Permalink |記事への反応(0) | 12:58

ツイートシェア

2014-04-28

■「戦後の韓国の慰安婦制度の使用」に関する海外 研究

韓国を訪問したオバマが「慰安婦はとんでもない人権侵害だ」と発言した。

それに対して安倍総理は「筆舌に尽くしがたい思いをされた慰安婦の方々のことを思うと本当に胸が痛む思い」だとし、

「２０世紀は女性を始め、多くの人権が侵害された世紀であった。人権侵害が起こらない21世紀にするため、日本も大きな貢献をしたい」と述べた。

これはちょっと意外な発言で、日韓のメディア、右派左派ともにちょっと戸惑った感じがしたように思える。

安部首相の真意がどういうものなのか、これからの行動を見ないと分からないが、

これは、慰安婦に対する人権侵害を認めつつ、「慰安婦制度をやっていたのは日本だけでなかった」という文脈を作ろうとしているのかなと思えた。

それはオバマの発言に対して、「米軍慰安婦はどうなんだ」「朴正煕の韓国軍慰安婦管理はどうなんだ」という反応が多く見られたものを反映していると思う。

「20世紀」という一般化といい、正直なかなかうまい手というか、慰安婦問題に対して右左をなだめる、これまでにないスタンスになるかもと思った。

そうなってくると、戦後の韓国の慰安婦制度が本当にあったのかという話になってくる。あったなら、慰安婦像を海外に建てるキャンペーンが別の意味を持ってくる。

別に「あいつらもやってから、俺らは悪くない」という意図ではなく、

実際問題として、日本が謝罪もし、アジア女性基金も設立した一方で、韓国自身が実は同じ問題を抱えていたのに黙殺するという事態は、事実を明らかにする上でも好ましくないと思う。

まとめサイトではソースがあいまいなものも含めてよく目にするが、いくら内輪で盛り上がっても意味は皆無で

海外でどのようにどのように研究されているか、というのが重要になると思う。

残念ながら、メディアという点では海外では概して「20万人の韓国人が日本に性奴隷にされた」「日本はその歴史を否定しようとしている」という文脈で報じられているのがほとんどだ。

しかし、アカデミズムの分野では、ここ最近韓国自身の慰安婦制度に目を向けられているものも増えているように見受けられる。

おおよそ中立的な立場であると見受けられるC.Sarah Sohという研究者の2009年に出版された"TheComfort Women"という本は海外でも評判が高いようなので、色々調べようと思った。

http://www.goodreads.com/book/show/6068978-the-comfort-women

検索すると、Google Readersで一部内容が見ることができ、その部分にちょうど韓国の慰安婦制度について記述しているところがあったので、メモ代わりに引用しておく。

もちろん、この本は、日本の慰安婦制度、および人権侵害にも厳しい目を向けているが、

この部分の結論としては、韓国は慰安婦生存者を日本の抵抗のシンボルとして英雄扱いする一方で、韓国自身の慰安婦制度含む性の人権侵害には目を向けてこなかったということを言っている。

「韓国が戦後慰安婦制度を使用してきた」という事実は、単なるネット右翼のデマではなく、海外の研究者にも裏付けられている事実であり、もっと注目されるべきではないかなと思う。

"TheComfort Women:SexualViolence and Postcolonial Memory inKorea andJapan"by C.Sarah Soh

(p:211～)

Camp TownComfort Women

Afterits liberation fromJapanese rule inAugust 1945,theKorean Peninsulawas divided intotwo: Soviet troops occupied the northern half and the US military the southern half. Theongoing US military presence in SouthKorea led to the formation and maintenance of “Camp towns” (kijich’on, inKorean) around the militarybases, a development that has had a striking social impacton Korean communities. Kijich’on (literally,base or camp [kiji] village [ch’on]) refers to the civilian world of commercial establishments and residential buildings that have sprung up around the US militarybases and cater to theneeds of the AmericanGI’s.It is “ a place whereKoreansand Americans- mostlymale military personnel- meet in an economic and emotionalmarriage ofconvenience”.As of the end of 1996, 37,000 American troops supported the economies of ninety-six kijich’on. The estimatednumber of kijich’on prostitutesover the first four decades of the American presence rangesbetween 250,000 and 300,000.

(中略)

The kijich'on sex trade consolidated and expanded duringthe second phase, which beganwith theKorean War. Inher testimony, PakSun-iwho had labouredat three different comfort startions inJapan 1944 to the end of thewar, recalled:

"At twenty-seven years ofage, Iwas having a hardtime makingends meet in Tongduch'on (the largest kijich'on just outsideSeoul). I ended up cohabiting with a staff sergeant of the USArmy for abouttwo years...One of myfriends from thedays at a comfortstation inJapan also workedas yang-gonju, butshe passedaway."

An Americanveteran who served inKorea in the 1950s after the end of theKorean War recounted that on Friday nights half-ton trucks would bring into thebase a few hundred women tostay the night or the weekendwith the soldiers. In 1958,five years after the armistice, the majority of about 300,000 prostitutes inKorea reportedly served American soldiers. Some of them, like their earlierJapanese counterparts(RAA), married and emigrated tothe United Statesas wives of servicemen.

"Specialcomfort women" for theKorean army

The fact that theKorean military also availed themselves of the "special comfort unit" during theKorean War has receivedlittle publicattention even after theKorean women's movement in support of the "comfort women" began in the 1990s.Only piecemeal anecdotal materialson it had come tolight from memoirs writtenby retired generals and generals and the testimony of soldierswho fought in thewar.

(中略)

Characterizing theKorean military comfort systemas an "unfortunate offspring" of theJapanese coloniallegacy, Kim Kwi-ok called for victimized women, civic organizations, and scholars to cometogether and confront the unresolved issues of this historical injustice. The media reports of Kim's work, however, have generatedlittle response. Therehas been no public outcry regarding theKorean military's use of "comfort women" during theKorean War orits violation of women'shuman rights.Korean silenceover these issues is reminiscent of earlier societal indifference toward survivors of imperialJapan's comfort system,It mirrors the reticence of manyJapanese to come to termswith the history of their country'swar time comfort system.As in thecase ofJapan, many inKorea, including retired military leaders, apparently regard the women'ssexual labour simplyas the performance of gendered customarysex labour in order to meet theneeds of fighting men.It is noteworthy that military authorities have acknowledged that the system of special comfort units contradicts thenational policy of banning licensed prostitution. Nonetheless, they have insisted that the special units were created to fulfill an important strategic end.

(中略)

Conclusion

(日本人の韓国への売春ツアー、及び韓国人の東南アジアへの売春ツアーは看過されてきたが、という話の後）

However, whenit comes to the issue ofJapan'swar time "comfort women" system, whichhas been redefinedby theinternational communityas a prominentcase ofviolence against women in armedconflict, no social critic or public intellectual inKorea would dare totake the customary masculinist position that such a system benefits the economy or promotesnational security. This is because thecomfort women issuehas been redefiendas militarysexual slaveryand a war crimeby theinternational community owing largely to women's collaborative movement for redress inJapan andKorea.

Still,little critical public discoursehas occurredon the legacies of that historical institution or the social structuraldimension ofKorea'Scomfort women tragedy. Few are willing to consider the unsavouryfact that, accustomed to indigenous public institutions that have granted customarysex rights to men, and licensedby the colonial government, manyKoreansdid not hesit ate to collaborate in recruiting and runing comfortstationsby trafficking ingirls and young women. Rat her than dealwith themessy and unpleasant complications of the historical record,Korean public discoursehas simplistically elevated the survivors toheroic symbols ofnational suffering underJapanese colonialism andits imperialistwar of aggression.

By contrast,Japan, which is unavoidably seenas the perpetrator nation,has been in turmoilover contested representations of thecomfort women phenomenon andits responsibility in the matter. Meanwhile, theinternational -as wellas domestic - trade in publicsex prospers in capitalist economies ofJapan andKorea despiteendless incidents of criminal abuse of women so employedby both foreigners and compatriots. The social historical legacies of masculinistsexual culture and political economic realities in thetwo countriescontinue to help construct women'Ssexual labouras stigmatized yet customary care labour for masculine "need".

Permalink |記事への反応(1) | 18:22

ツイートシェア

2013-02-24

■渋い

The publication in France of ourbook Impostures Intellectuelles [1] appears to have created a small storm in certain intellectual circles. According to Jon Henley in The Guardian, we have shown that ``modern French philosophy is a load of oldtosh.''[2] According to Robert Maggiori inLibération, we are humourless scientistic pedantswho correct grammatical errors inlove letters.[3] We shalltry to explainhere why neither is thecase.
Some commentatorsgo farther, attacking not our arguments but ouralleged motivations for writing thebook. Julia Kristeva, writing inLe Nouvel Observateur, accuses us of spreading ``disinformation''as part of an anti-French politico-economic campaign[4];she was even quoted (we hope misquoted)by theItalian daily Corriere della Seraas saying that we should undergo psychiatric treatment.[5] Vincent Fleury and YunSun Limet,again inLibération, accuse us of seeking to divert research funds from the social to thenatural sciences.[6] These defences are curious: for even if our motivations were indeedas ascribed (and they most certainly aren't), how would that affect the validity or invalidity of our arguments? We have the modest hope that calmerheads will soon prevail among both our supporters and our critics, so that the debate canfocus on the substantive content of ourbook.
Which is what? Thebook grewout of the now-famous hoax in whichone of us published, in the American cultural-studies journal Social Text, a parody article chock-full of nonsensical, but unfortunately authentic, quotes about physics and mathematicsby prominent Frenchand American intellectuals.[7] However,only a small fraction of the ``dossier'' discovered during Sokal'slibrary research could be included in the parody. After showing this larger dossier to scientist and non-scientistfriends, we became (slowly) convinced thatit might be worth makingit available to a wider audience. We wanted to explain, in non-technical terms,why the quotes are absurd or, in manycases, simply meaningless; and we wanted also to discuss the cultural circumstances that enabled these discourses to achieve such prominence and to remain, thus far, unexposed. Hence ourbook, thenoise and the furore.

Permalink |記事への反応(0) | 12:16

ツイートシェア

Movatterモバイル変換

「d dur」を含む日記

■米津玄師がLemonのPVでヒールの靴を履いている理由

■Dehradun Call Girls | skokkacallgirl

■打上げ成功/失敗のWikipedia的定義

Tattoos Hurt Your Chances of Getting a Job

Tattoos Hurt Your Chances of Getting a Job

■attracting commerce. Conditionson theisland improved during the Taiping Rebellion in the 1850s, when manyChinese refugees, including wealthy merchants, fled mainland turbulence and settled in the colony.[16] Further tensionsbetween theBritish and Qingover the opium trade escalated into

■clang:warning: argument unused during compilation: '-export-dynamic'

■vimをtinyでmakeするとエラーが大量に出るんだが

■「戦後の韓国の慰安婦制度の使用」に関する海外研究

■渋い

■attracting commerce. Conditionson theisland improved dur ing the Taiping Rebellion in the 1850s, when manyChinese refugees, including wealthy merchants, fled mainland turbulence and settled in the colony.[16] Further tensionsbetween theBritish and Qing over the opium trade escalated into