  |
はてなキーワード: NO WARNINGとは
Refuting the “Israeli” Claims Regarding Evading their responsibility for the Massacre of the Gaza Baptist Hospital
Today, the “Israeli” Occupation Entity is trying to evade their responsibility for the crime of bombarding the “Baptist” Arab National Hospital in Gaza City, which the Israeli” Occupation Forces (IOF) committed on the evening of Tuesday, 17 October 2023. This heinous crime was committed against innocent Palestinian civilians while taking the hospital as a shelter from the flames of the “Israeli” brutal aggression, which left nowhere safe in the besieged enclave. It is necessary to affirm that, the Baptist Hospital belongs to the Anglican Episcopal Church in Jerusalem, and was built before the occupation of Palestine.
It is obvious that the “Israeli” enemy has been spreading lies since the very beginning of his destructive war on our people, when he with no single evidence claimed that the Palestinian resistance killed children, cut off heads and raped women. In continuation of this series of lies, they tried to evade their crime, attributing it to one of the resistance factions. Accordingly, we present some of the conclusive evidence to prove the “Israeli” Occupation Entity responsible for this heinous crime:
1) It is no secret that the IOF, several days ago, threatened several hospitals in the Gaza Strip, contacting each hospital separately and requesting their evacuation and holding the hospitals directors responsible for the consequences of neglecting the threats. In fact, there are dozens of clear statements from the IOF spokespersons in this regard.
2) Since the beginning of the ongoing aggression, the “Israeli” army has ignored the principle of distinguishing between civilian and military targets. Thus, the bombardment has systematically targeted emergency services, ambulances, civil defense facilities, schools, mosques, and churches.
3) The IOF contacted the directors 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 geographical scope of “Israeli” military operations. In this regard, the official spokespersons for the IOF plus a number of hospital directors conducted interviews live on Al Jazeera, revealing the premeditated intention of the IOF to target hospitals in the Gaza Strip.
4) On 14 October, 2023, at 20:30, the IOF fired two shells towards the Baptist Hospital, and the next morning they called the hospital director, Dr. Maher الصفحة 2 من 3
Ayyad, saying to him: “We warned you last evening with two shells, so why have you not evacuated the hospital until this moment?!” Following that call, The hospital director contacted the bishop of the Evangelical Church in Britain and informed him of the incident, who in turn contacted international organizations before sending the hospital a message reassuring them that they could remain in the hospital. Yet with no warning, the IOF airstrikes returned, on Tuesday evening, to carry out the massacre against the hospital and the shelter-seekers of the displaced innocent Palestinian civilians.
5) Immediately after the massacre, the IOF spokesperson quickly published a statement on his page on the “X” and “Telegram” platforms at 21:17, which stated, “We had warned the evacuation of the Baptist Hospital and five other hospitals so that the Hamas terrorist organization would not take as a safe haven”. That statement is a clear claim of this massacre, and it is documented with a “screenshot” image attached to his page on Telegram, but he quickly deleted the post after seeing the massive scale of the massacre for the large number of victims, and the angry responses of the Arab, regional and international communities. Later on, he disavowed it, publish another
statement denying that he had issued the first statement.
6) Before and during the event, the resistance factions did not fire any missiles at the occupied territories, the “Israeli” sirens did not activate, and the Iron Dome missiles were not launched. Moreover, dozens of reconnaissance drones do not leave the sky of the Gaza Strip (365 km2 ), photographing and monitoring every inch around the clock. If the massacre was due to the resistance’s missiles, as the “Israeli” Occupation Entity falsely claim, why would not they show one picture their claims?!
7) The “Israeli” Occupation Entity claimed that this massacre was caused by a missile launched by the Islamic Jihad. However, we would wonder how they could identify and distinguish between the missiles of the resistance factions immediately after they were launched?!
8) The IOF military system documents and records all their operations by day, hour, minute and second, and in all previous times their media outlets came out 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 the resistance’s missiles are somewhat “primitive” and do not have the destructive power that kills hundreds at one time. And throughout the history of previous confrontations and the current confrontation, no resistance missile has caused a tenth of this number of “Israeli” deaths.
10) The only video scene documenting the moment of the explosion reveals that the mass of flame and the sound of the explosion are identical to other “Israeli” bombs throughout the days of the ongoing aggression, which with no doubt proves that the “Israeli” origin of the missile.
الصفحة 3 من 3
The deliberate attack on hospitals is a war crime, stipulated in Article (8, 2, b, 9) of the Statute of the International Criminal Court. Accordingly, Hamas officially calls on the Prosecutor of the International Criminal Court to open an investigation into this crime, which falls within the framework of a genocidal war, in accordance with the provisions of Article 6 of the Basic Law. These bloody acts are also based on the policy of denial pursued by the “Israeli” Occupation Entity, as they deny the existence of the Palestinian people.
There is no doubt that impunity fuels crime, and investigating crimes is a way to protect people. Furthermore, if a legal and judicial response is necessary, it is above all that the response to this crime must be humanitarian and global. Such actions must shock the conscience of the world, or else there would no longer be a reliable international community if the “Israeli” Occupation government free to decide to bomb hospitals!
In conclusion, we are facing a genocidal massacre committed by IOF against children, women, and the elderly. The “Israeli” Occupation Entity is the only responsible for the crime, no matter how much they try to weave lies and fabrications to get away with it, as they always do.
The Islamic Resistance Movement
「ガザ・バプテスト病院虐殺の責任回避に関するイスラエルの主張に反論する」
って題名
オリジナルには入ってるのだろうか
This publications is a designated secure publication as per fleet
office regulation FSC 9801(d) Section 1. As a designated secure
publication, access to this publication is limited to legal adults with
free agent status. No minors or those placed under guardianship
shall have access to this publication. As a designated secure
publication, all unauthorized reproduction, broadcasting,
displaying, and/or disclosure provided to agents proper clearance
be fully prosecuted under the law. There will be no warning. As a
designated secure publication, citation or translation pertaining to
information disclosure process must be undertaken with the legal
department prior to any information transfer, citation and/or
translation. Furthermore, the falsification and/or elimination of
this clause from any reproduction of this publication does not in
any way or form lessen the illegality of the unauthorized
reproduction and/or translation. All violations will involve severe
legal punishment maximumallowable under the law. There will
be no warning.
おれはもうMooseしかつかわねぇ。後にも先にもMooseMooseMooseMooseMoose!!!!!!！！！！！１１１１１１１
ってな人の為にいつでもどこでもMooseする。automooseを実装しますた。
package automoose; use strict; use warnings; sub import { strict->import; warnings->import; } package automoose::before; use Moose; no Moose; package automoose::after; use Moose; my @before = keys %automoose::before::; my @after = keys %automoose::after::; my @exports = do { my %u; @u{@before} = (); grep { !exists $u{$_} } @after }; package UNIVERSAL; use Moose; for my $func (@exports) { __PACKAGE__->meta->remove_method($func); __PACKAGE__->meta->add_method($func,sub { my $class = shift; my $auto = $class.'::__auto__'; no warnings 'redefine'; local *Moose::_get_caller = sub { return $class }; Moose->import( { into => $auto } ); my $code = $auto->can($func); $class->meta->add_method($func,sub { shift; goto $code; }); goto $code; }); } 1;
使い方はいたって簡単。useするだけ。
use automoose; my $obj = Foo->new;
いきなりnewが呼べちゃう。
他にも
use automoose; Foo->has( hoge => is => 'rw' ,default => 9999 ); Foo->has( muge => is => 'rw' ,default => 7777 ); print Foo->new->hoge; print Foo->new->muge; Bar->extends('Foo'); print Bar->new->hoge;
ょーかんたん。げーべんり。
しっかしこれ、automooseだけど実装するの結構めんどかったのよ。Moose-0.44をベースに作ったんだけどさ。
Moose内部で使用している$CALLERって変数がレキシカルなもんだから、どうやってそれを外から制御すればいいのかすんごい苦労したわけさね。
で結局importの引数にinto渡してさらにMoose::_get_caller関数を上書き無理矢理ハックしたってわけさ。
でもね。でもね。でもね。ちょっと聞いてよ。
ふと最新のMoose-0.50見てみたらさ、Moose::__CURRY_EXPORTS_FOR_CLASS__なんて関数が定義されてるわけよ。
外から明示的に$CLASSを変更できるインターフェイスなわけよ。おいおいおいおい、勘弁してくれよ。こっちゃ折角苦労してハックしたのにあっさり公式対応するなってばよ。メゲルヨ？ぼく。
まぢめげるよ。めげる。ってかもうめげたよ。もうMooseなんてつかわんね！つかわんね！
Mooseなんて大嫌いだー！
俺はMooooooooooseをやめるぞぉおおおおおおおおお、ＪＯＪＯぉぉぉおおおおお！！！！１１
やってしまった・・・。
方針：
package SixtyLinesTemplate; use strict; use warnings; our $VERSION = '0.01'; sub convert { return unless defined(my $str = shift); $str =~ s{&}{&}gso; $str =~ s{<}{<}gso; $str =~ s{>}{>}gso; $str =~ s{\"}{"}gso; $str; } sub include_template { my $tmpl = shift; my %c = %{+shift}; eval convert_template($tmpl); die $@ if $@; } sub convert_template { my $tmpl = shift; my $cache = $tmpl.'.cache'; return scalar do { open my ($FH) , $cache; local $/; <$FH> } if ( -f $cache && (stat($tmpl))[9] <= (stat($cache))[9] ); my $out = do { open my ($FH) , $tmpl; local $/; <$FH> }; $out =~ tr/()/\x28\x29/; $out =~ s/\[%\s*(foreach|if|unless|end)\s*(.+?)\s*{?\s*%\]/");".(lc($1) eq 'end' ? '} print q(' : "$1 $2 { print q(")/ige; $out =~ s/\[%(.+?)%\]/);print $1; print q(/g; $out =~ s/\[#(.+?)#\]/);print SixtyLinesTemplate::convert($1); print q(/g; $out = 'print q('.$out.');'; open my ($FH) , '>' , $cache; print $FH $out; $out; } 1;
サンプルコード：
use SixtyLinesTemplate; my $context = { 'title' => 'Example', 'list' => [10,'<A&B>'] }; SixtyLinesTemplate::include_template('template.tmpl',$context);
サンプルテンプレート：
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>[# $c{title} #]</title> </head> <body> <h1>[# $c{title} #]</h1> <table> [% foreach my $i (0..@{$c{list}}-1) %] <tr bgcolor="[% $i % 2 ? '#FFCCCC' : '#CCCCFF' %]"> <td>[% $i %]</td> <td>[# $c{list}[$i] #]</td> </tr> [% end %] </table> </body> </html>
出力例：
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>Example</title> </head> <body> <h1>Example</h1> <table> <tr bgcolor="#CCCCFF"> <td>0</td> <td>10</td> </tr> <tr bgcolor="#FFCCCC"> <td>1</td> <td><A&amp;B></td> </tr> </table> </body> </html>
foreachんところが汚く見えるかもしれませんが、あれは添え字を取ろうとするとああなるんでご勘弁を。
普通にループするだけならforeach my $item (@$c{title}) でいけますゆえ。
あと存在しない変数とか使うと死んだり警告でたりするのでevalの前にno strictとno warningsをやった方がいいかもねぇ。
って何まじめに検証してんだ俺・・・orz
追記：
SixtyじゃなくてFortyだね。恥ずかし！
追追記：
でも＆amp;の奴はちゃんと書いてるんだけども投稿すると勝手にエスケープされてしまってるんだよね。何でだろ？
ちなみにこのconvertの処理はCGI::Utilから拝借しました。
