Xx Xx Local: Fill & Download for Free

The number format for a swiss mobile phone number is the following:+41 7{5,6,7,8,9} xxx xx xx when called internationally07{5,6,7,8,9} xxx xx xx when called locally+41 is the country calling code for Switzerland075,076,077,078,079 are national destination codes used by various mobile providers. The zero must not be dialled when calling internationally.xxx xx xx are the seven digits reserved for the subscriber phone number.

Well, that's quite interesting question.We have 23d of February, "Fatherland Defender's Day", when we thank anyone who served their country in the armed forces at any time in their lives (of course, professional officers are celebrated more than conscripted soldiers). The problem is that this holiday degraded for some reasons into just "Man's Day", as opposite to "Women's Day", the 8th of March. Quite unfair and disputable, it raises hell of a shitstorms each year, "why don't we thank women who served and thank those men who didn't serve just because they are men and supposed to serve in the future", etc,etc,etc.We also have Victory Day to remember all the fallen and survived veterans of WW2, who fought for their country. This can be described by an old song line, "celebration with the tears in the eyes". Celebration - because it is the Victory day, after all. We won. Prevailed. Against all odds. "With tears" - because the Victory was costly. No victory is ever cheap, and, as Churchill said, "no matter how high is the price of a victory, it will never be lower than the price of a defeat", but hell, way too much blood was spilled, lives were lost and tragedies happened. Almost ANY family on ex-USSR territory will have AT LEAST one member or relative who fought in WW2, lots never returned or were wounded. This is a very deep scar on collective psyche of Russian population, impossible not to remember.But some battles earned additional attention in our culture. Honestly, we are prone to celebrate local battles too, in the regions that were mostly affected by them. Say, in Moscow, 5th of December is celebrated (unofficially, of course) separately (on this day in 1941 Soviet Forces went on counteroffensive, routing Germans away from Moscow).And Stalingrad and Siege of Leningrad... well, they are those local battles that earned their celebration and remembrance.Stalingrad in popular remembrance is the total, utter hell on earth. The concentrate of pain, violence and suffering of all parties, death and destruction, with heroism and tenacity.Victory in the Battle of Stalingrad, February the 2nd is officially one of the "Days of Military Honour" (Days of Military Honour - Wikipedia) that are celebrated in the Armed Forces mostly, but in civilian world this day is probably noticeable only by higher percent of WW2 films on the TV.As for the common people, they tend to remember it if they have some personal connection to the battle. Most of the citizens of modern Volgograd qualify, too.Remembrance mostly consists of remaining the fallen, triumph and tragedy of this battle.The biggest memorial, Mamaev hill:It is literally the mass grave for 35.000 of Stalingrad defenders. No surprise memorial is more a memorial to the fallen than to the battle itself.Near the Monument of Motherland there is this remembrance hall:A huge round hall, with Eternal Fire in the centre, and lists of fallen in the battle on all the walls. This is more of a shrine, a cemetery, to remember and honour the fallen in this battle rather than battle itself. An eerie place. Fantastic acoustic there. The slightest whisper is amplified by the walls.And the Honour Guard, of course. When they perform Change of the Guard and march out of the memorial, this sounds of their boots, echoing from the walls... god, it is better to see and hear once than try to explain:The hall, the Change of the Guard (close to the middle part of the video), everything.Note fresh flowers. There are always fresh flowers, people keep carrying them. To the Tombs of the Unknowns, to the Memorial Hall, to the General Chuikov's Grave. All the time. People remember. And what's important, they remember the tragedy of this battle. It is impossible NOT to remember it.Leningrad. Hm. This is a bit different.The firs cultural associations are, of course, "125 Siege's grams <of bread rationing >, With fire and blood in twain" (Leningrad's Poem by Olga Bergoltz), "Nevskiy <prospect, main street of Leningrad, much like 5th Avenue in NYC)> was full of poster, every wall was screaming "During artillery barrage, this side of the street is most dangerous" <From Ballad of Raven Mountain> (sorry for my shitty translation, fucked up the rhyme but kept with literal meaning of these poem excerpts), Second Symphony of Shostakovich, Tanya Savicheva's Diary (Little girl, 6 y.o. kept writing diary during the siege. It all boils down to deadly serious notes "Sister diead at XX;XX DD:MM;YY, Brother died at XX;XX DD:MM;YY, Uncle died at at XX;XX DD:MM;YY, Granma died at XX;XX DD:MM;YY, Mum died at XX;XX DD:MM;YY. Savichev's are dead. All dead. Only Tanya remains alive". She will die too, much later, after the city will be relieved due to TB and malnutrition.That's it. Personal diary of a young, innocent 6 y.o. girl, writing in bad, children's cursive about death of all her parents and relatives, until she remained the only one alive.Road of Life, Ladoga Lake as only source of supplies and constant heroism to keep supplies flowing.The never-ending air raids and barrages, Iconic Metronome (air raid warning was broadcasted by a metronome ticking, fast pace - attack in progress, low pace - all clear). Some called it the heartbeat of the city.Or another iconic thing from the Siege of Leningrad:“Citizens! During artillery shelling, this part of the street is the most dangerous!”(Germans had guns on Pulkovo Heights, to the south, this makes northern parts of the streets most dangerous due to shell trajectory).So, as you can see, while Stalingrad is a hell on earth, the embodiment of WAR, WW2, military heroism and sacrifice, Leningrad is first and foremost remembered as CIVILIAN sacrifice and heroism. Of course, there was a hell of a fighting, Nevskiy Pyatachok for example () A small bridgehead, 1-2 km long frontline, utter meatgrinder (160.000 dead Germans and ~250.000 dead Soviet per 1.5 km of frontline, that's goddamn small Verdun!), but this is sort of faded in people's memory, while civilian suffering is widely remembered.How people died of malnutrition and cold on 125g of rations but kept factories working, how people were defiant until their death. That the War is not somewhere distant, it is right there and you are gonna suffer, fight and die no matter who you are, military or civilian.And right here, in my opinion, the tragedy and suffering is what is remembered even more.Just have a look at the memorial:Doesn't look like a memorial to heroic victory, does it?Well, I hope it answers your question.

I gather that it has to do with the fact that a single executable can be coded in many different ways?Yes. This is an important part of the problem but there is a little more to it.This is going to be difficult to answer effectively while keeping jargon and technical information to a minimum. Canonically, code and data aren't differentiable in executables but I'm not sure how much of a problem this is in an x86 executable (aren't there .text and .data segments?) so I won't comment on it. A more pervasive problem is that information gets lost and changed during compilation. I doubt I will be able to come up with a comprehensive list but I'll try to come up with a few examples.Since I'm the first person to answer, I'll start with two pieces of low hanging fruit. (1) Comments are lost in compilation. (2) Identifiers (function names and variable names) are lost in compilation.// This line and he line directly below it are comments. // This function computes n! recursively int factorial(int n) {  if (n < 2)  return 1;  return n * factorial(n - 1); } You don't need to know what that code does or how it works to understand the consequenses of (1) or (2). The best reconstruction you can possibly hope for would look like this.int proc_0(int local_0) {  if (local_0 < 2)  return 1;  return local_0 * proc_0(local_0 - 1); } Once again, this is a best case scenario. The function is less readable and you no longer have any explanations the author considered important. Otherwise, it is exactly the same.For technical or very curious peopleWhat phase of compilation are the identifiers lost? This is actually kind of difficult to answer definitively (it must vary a little from compiler to compiler). If anyone cares to comment, I would like to know more about this. Information would certainly be irrevocably lost at whatever step produces machine code. Lets say I'm using an instruction set with labels and two instructions.label:addi register register num (add constant) => 0 xx xx xxjne register num label (jump if not equal) => 1 xx xx xxThis codestart: addi R1 R1 1 jne R1 3 start would get assembled into0010101 1011100 // The assembler has to replace the label name with the address of the instruction that follows that label Goodbye forever label name. All you have now is the address. Local variable names would have been lost already. This is bad enough by itself but it would be even worse if there were two labels in the same location (is that a realistic concern?).Everyone else, start reading againAnother problem for decompilation is that compilers perform a optimizations that may significantly alter code.int dot(int a[20], b[20]) {  int x, result = 0;  for (x = 0 ; x < 20 ; x++)  result += a[x] * b[x];  return result; } The previous function might be optimized to conceptually look more like this (called loop unrolling).int dot(int a[20], b[20]) {  int x, result = 0;  for (x = 0 ; x < 20 ; x += 2) {  result += a[x] * b[x];  result += a[x + 1] * b[x + 1];  }  return result; } It would do this because you pay a little overhead (one add, one comparison, one jump) for each iteration of the loop so reducing the number of iterations will make the function a little faster. This is a simple function and only one simple optimization. I'm not sure how unrecognizable gcc could render less trivial functions (there might not be enough high level optimizations like this to be a huge concern. I honestly don't know).For a more specific example, consider the inline keyword in C.inline int max(int x, int y) {  return x > y ? x : y; }  int main() {  int x = 4, y = 6;  if (max(x, y) < y)  y = max(x, y);  return 0; } The inline keyword basically instructs the compiler to insert the function's body wherever it is called in the code. It might help to picture it like this (but the compiler doesn't actually perform a text replacement for inlines).int main() {  int x = 4, y = 6;  if ((x > y ? x : y) < y)  y = (x > y ? x : y);  return 0; } There is just no way to know that there was originally a function call at lines 9 and 10 in the original code.I'm sure that there are a lot more little issues like these that compound on each other and make it damn near impossible to reproduce code that a human can make any sense of.