oguzpedia

Salomon Singer - Mutexes & Semaphores Demystified @ Barr Group, 13 May 2015

2016-01-13T18:58:00.002+02:00

Summary @ 46:48

Summary @ 47:16

For the 54 minutes video: https://vimeo.com/128176447

Salomon Singer, mailto:ssinger@barrgroup.com, is the principal engineer at the Barr Group having 30+ years experience in embedded systems. In this excellent talk, he explains the mutexes and semaphores and emphasizes the differences between them. Please note that in the Internet there are a lot of wrong information on how mutexes and semaphores differ!

I took the following notes while watching the excellent talk:

11:25 Salomon Singer starts his talk after Michael Barr's introduction on
the Barr Group etc.

12:45 Code at risk due to shared resources is called critical section. Left
unprotected we might have race condition.

15:00 Tasks are like cars approaching an intersection. Need a protocol to
prevent mishaps.

16:00 Mutual Exclusion: the programmer should be involved for protecting
the critical sections.

17:00 Mutex is an operating system data structure to ensure that tasks have
exclusive access to shared variables or hardware resources. It is
short for "mutual exclusion". It is used to prevent race conditions.

17:30 Pseudocode:
Acquire mutex
    // Critical section code
    Release mutex

17:55 Each mutex protects one shared resource.

18:30 Bathroom key analogy: only one person may use the bathroom at a time.
Mutex: bathroom key
Tasks: customers
Shared resource: bathroom

19:00 One conceptual implementation:
typedef struct {
TCB *p_block_q; // queue of blocked tasks: a linked list
// of waiting tasks
// NULL if there is no waiting task
int value; // current mutex state: 1 -> available
} mutex_t; // 0 -> not available

20:00 Each mutex is created at the request of a task. Pseudocode:
// allocate space for a mutex
m. p_block_q = (TCB *)NULL; // no tasks waiting
m.value = 1; // initially available
return &m; // return a handle

20:42 Mutexes are totally scalable solution: if N tasks try to acquire the
mutex, only the first one will succeed and N - 1 tasks will wait in
the queue. When a tasks releases the mutex, one task in the wait queue
will be ready.

21:26 Summary: a mutex is created in the available state. Always use a mutex
by protocol. Never release a mutex previously not acquired.

22:32 What if two tasks call the same function at about the same time?
Each such function must be reentrant! Non-reentrant functions are
the source of many problems that are extremely difficult if not
impossible to reproduce.

24:30 Requirements for reentrancy:
- Safe to use automatic variables: each task has its own stack.
- Unsafe to use static or dynamic variables: unless protected
  with mutexes.
- Peripheral registers: access must always be protected!

25:30 Example: TCP/IP networking. The network driver controls just one
chip just like a global variable.

26:50 Reentrant functions are the best places to use mutexes.

27:27 Where and when to use mutexes:
Rule 1: Use mutexes in "leaf node" source files, i.e. in source
files that don't make calls to any other source files.
Rule 2: Avoid mutexes in "task level" source files. Prefer
directional intertask communication like semaphores,
mailboxes or message queues.

28:40 What is semaphore? It is an RTOS-provided data structure, at core
an integer counter. Safe for parallel-running tasks. All the data
structure updates inside the RTOS are atomic.

29:15 Types of Semaphores:
- Counting Semaphore: a multitasking safe counter. Can be
incremented/decremented automatically via API calls.
- Binary Semaphore: Can be set to 1 or 0 automatically via API
calls.
- Mutual Exclusion Semaphore (Mutex): A special binary semaphore
with additional capabilities.

30:10 One conceptual implementation:
typedef struct {
TCB *p_block_q; // queue of blocked tasks: a linked list
// of waiting tasks
// NULL if there is no waiting task
int value; // current state: 0..N
} sem_t;

30:45 OS Implementer: similarities keep coming!
OS user: try to forget you ever saw this!

30:55 Because semaphores and mutexes have completely different uses!

31:20 ISR's can only make non-blocking calls:
- It is never safe to wait for a semaphore.
- However, it is safe to signal a semaphore: that will never block!

31:55 Tasks can safely wait and signal a semaphore.

32:00 Mutexes vs Semaphores:
- Mutexes are to be used only for mutual exclusion. Always
init 1, wait() first and then leave().

32:30 - Semaphores are for one-to-one signalling. Can be init to any
value. Typically init to 0. There is no prescribed order to
use the API.

34:10 Problem: multiple identical resources. Analogy: 2+ bathrooms.

34:35 If you Google this problem, many sources say a counting semaphore will
work! They are all wrong. A counting semaphore can't protect 2+
resources! Need to know which one is available.

34:55 The right solution will be using distinct mutexes for each bathroom. One
key for women and another key for men.

35:28 Priority inversion problem.
A high priority task needs a resource being used by a low-priority task.
So, it is waiting for the low-priority task. However, a medium-priority
task preempts the low-priority task having higher priority!
Consequently, the high-priority tasks wait for the low-priority task
longer than necessary! It may cause the high-priority task to miss a
deadline.

37:48 What is the implications of priority inversion? It is impossible to
be certain that all deadlines will be met! Thus, we need a way to
prevent priority inversions.

38:35 Priority inversion workarounds for mutexes:
- Highest locker or priority ceiling protocol. Can be implemented
above the RTOS. Each shared resource is assigned a priority just
above its users' priorities. Calls to raise and lower task
priorities are used instead of mutex calls.

39:28 - Priority inheritance protocol. Can be implemented only in the
RTOS. The priority of a task that holds a resource is increased
automatically but only when a high-priority task wants the resource
and only until the low-priority task releases it. Upon completion,
the priority of the task will be demoted. It scales nicely.

40:00 Priority ceiling example.

41:18 Priority inheritance example.

42:43 Priority inheritance scales nicely example.

44:34 Mars Pathfinder story: priority inversion example. WxWorks has a mutex
priority inheritance option, but it wasn't turned on!

47:50 Starts to answer the questions.

Prof. Allen B. Downey - Introduction to Semaphores @ 2010

2016-01-08T19:00:00.002+02:00

Making a demo with Sync @ 17:05

For the 60 minutes video: https://www.youtube.com/watch?v=RaEUw107dpg

In this video Prof. Allen B. Downey talks about concurrency basics and semaphores. He makes nice demos with his Python Sync app. This is a nice video for introduction to concurrency.

36:50 Starts to talks about free books.

44:25 Starts to answer the questions.

Scott Meyers – The Most Important Design Guideline @ ConFu, Latvia, 13 Nov 2014

2016-01-07T18:19:00.000+02:00

Summary @ 57:18

For the 59 minutes video: https://www.youtube.com/watch?v=5tg1ONG18H8

The Most Important Design Guideline? article by Scott Meyers is about the similar topic.

Scott Meyers talks basically on the interface design. I took the following notes while watching the excellent talk:

00:24 I want to talk about single most important guideline I know
of writing software independent of the its language, its tasks, its
users, etc.

00:50 #1 Make interfaces easy to use correctly and hard to use incorrectly.

00:55 We spend a gigantic amount of time on interfaces!

01:40 There are two types of interfaces.

01:45 #1 Encountered by everybody:
GUI/Software interfaces
Command line interfaces
Speech interfaces

01:50 #2 Encountered by software developers:
Library interfaces
Module interfaces
Class interfaces
Method and function interfaces
Generics and template interfaces

04:00 Interface users are typically smart and motivated.

05:00 If they use your software improperly, it is your fault!

05:27 What this means is that software should be designed and implemented
to be easy to correctly and hard to use incorrectly.

06:05 The software development industry should shoot for Rico Mariani's
"pit of success".

06:20 It means by default all forces should push you in the right direction.

06:46 Principle of least astonishment: strive to maximize the likelihood
that user expectations about an interface are correct.

07:30 Your job is to maximize the odds that the guesses are correct.

07:42 If users can do something, it should do what they expect.

07:55 If users know what they want to do, they should be able to guess how
to do it.

08:20 UI counterexamples:
Starting from Win 95, press the Start button to shutdown the computer.

08:45 The rationale was "everything else we tried was worse".

09:12 What is biggest complain about Win 8? It doesn't have a "Start" button!

09:40 If your interface is so liked & so long-lived, be proud of it!

10:45 [In an old Mac OS] in order to eject the removable media, drag its icon
to the trash can!

12:25 In Win XP, choosing the large font size instead of the normal one was very
problematic!

13:10 While installing Qt 4.8 on a Win computer, "The install path must not
contain any spaces..." Pointing to poor porting from Unix!

15:45 Expedia and Kayak's calendar selection UI's in 2010, i.e. after iPhone:
Kayak allowed swipe, but Expedia didn't!

16:20 Some interfaces are so bad, it is really difficult describe exactly what
is wrong with them! A very poor UI example from a calendar app.

18:15 Slate mobile app for reading articles: the "Top Comment" inserted into
the middle of article!

19:40 General techniques:
- Avoid gratuitous incompatibilities with the surrounding environment:
take advantage of what people already know
- Offer natural syntax
- Offer intuitive semantics:
In API's, when in doubt, do as built-in or standard library types
do. In GUI's, try to have mouse clicks, keyboard shortcuts and
gestures mean the "usual things".

22:25 More specific techniques:
- Choose good names: the very first impression that people get is based
on names!

24:50 UI counter example: Adobe Acrobat 9 after modifying a PDF displaying a
dlgbox with three buttons: "Do you want to save changes to your file?
Yes, No, Cancel." What does "Cancel" mean is confusing!

25:45 OpenOffice has a similar "Save, Discard, Cancel" dlgbox!

26:30 Being desktop apps, i.e. space isn't so restricted, you can put more
text on the "Cancel" buttons.

26:45 Another solution, without asking silently saving the file which brings
other UI challenges.

27:05 One of things I find is that if you have UI challenge that is making
difficult for people to do the right thing try to come up with an
alternative design that makes the problem completely go away!

27:25 "Gulf of execution": distance between what you want to do and the action
you must take to get it done. Larger the gulf of execution, the more
difficult to use the software.

28:00 As interface designers, our goal is to minimize the "gulf of execution"
and turn it into "pit of success"!

28:45 "Choose good names" API counterexample: In C++ equal_range is based on
equivalence, not equality!

29:05 Be consistent in all kind of things: in naming, in error reporting etc.

30:15 "Be consistent" GUI counterexamples:

31:20 - "Mail Compose button" on different locations on iPhone, iPad and MAC
OS X! Works against muscle memory...

32:28 "Be consistent" cross-device counterexamples:
- Marriott Rewards Card. It carries numbers grouped by blanks. The web
UI accepts the spaces, but the server rejects the number submitted!
Stupid UI designers...

- An ATM UI asks for cash or check deposit, but the hardware buttons
are placed below the wrong UI buttons! Misleading...

34:10 - Java container size? both "length" and "size" used!

34:40 - .NET 1.0 container size? both "Length" and "Count" used! People
claims thanks to the IDE, no problem. But they are wrong on two
counts:
1 - "L" and "C" are different letters!
2 - Not always an IDE is used!
Plus, as .NET supports reflection, you have to query the objects for
more than necessary!

36:40 - C Standard Library file functions: fscanf(), fgetpos() and fseek()
gets the FILE pointer as the first argument. However, fgets(),
fputc() and freopen() gets the FILE pointer as the last argument!
Even very very experienced C developers are confused:
"This inconsistency has frustrated millions of developers for more
than 30 years" - Ferenc Mihaly

37:59 - C++ Standard Library function to eliminate all container elements
with a given value: for 8 containers erase() and for 2 containers
remove() are used! I am intimately familiar with the developments in
C++ there are reasons for it and the reasons are not good! The smart
people never looked at the problem at this level, but the programmers
look at this level!

39:20 - C++ Standard Library: if the sort() function doesn't run in N * logN
time which can be detected during compilation, the code it
rejected! However, binary_search() either runs in logN or N.
Conceptual inconsistency...

41:20 - C++ Standard Library: have sort() and stable_sort(), however
list::sort() specialization is guaranteed to be stable! Inconsistent
naming...

42:30 Progressive Disclosure: discriminate between "expert" and "normal" not to
overwhelm the users. Not uncommon in GUI's.

43:45 - GUI from an app called SUPER: categorized the options. Categorization
alone may be fine, but it is just not progressive disclosure!

44:20 - Applicable to API design, too: bundle advanced functionality into
separate objects. Functionality is hidden, unless such objects are
requested. Ken Arnold's "Programmers are People, too" article cites
Java JButton class offering >100 methods. However, typical use only
a small minority! His suggestion: retain only commonly-used methods
in JButton, bundle rarely-used method into an object accessible via
JButton's getExpertKnobs method. Plus, bundle integration
functionality into an object accessible via getIntegrationHooks
method.

46:20 Document Before Implementing: proven way to discover interface problems.
Unpleasant to explain -> unpleasant to use. Plus:
- Surprising or underspecified behaviors
- Bad names
- Inconsistencies

47:20 If you are using a strongly typed programming language, i.e. statically
typed, the type system is your friend. Many errors can be prevented through
stronger typing.

47:40 C++ Date class:
Date(int month, int day, int year);

48:20 If in an API, any time adjacent parameters are of the same type, callers
can pass them in wrong order! It should be avoided as much as possible.
Easy to use incorrectly!

48:45 Fix it by introducing Month, Day and Year types.
Date d(4, 8, 2005); -> Date d(Month(4), Day(8), Year(2005));
Besides preventing the user errors, the code is now easier to read.

49:49 Typedef's are synonyms and using them for int's make the code easier to
read, but compiler doesn't detect errors! Programming to make you feel
better about yourself! You haven't improved the type safety in any way...

50:30 Why I fixated on 4/8/2015? The day we got "Darla". My wife and I have no
kids, having a dog is good!

51:30 Constrain values: Month(-4) is still possible! Let the Month class has
public static 12 const Month objects per actual month and disable new
Month object creation, i.e. let the Month ctor be private and explicit.
So, Month(-4) won't even compile!

52:40 Addressing the day and year is harder, but it is possible.

52:52 When you design an interface, you should always ask yourself what kinds of
errors might people make in this interface.

53:00 Given the errors they could make, what actions can we take to prevent them?

53:15 Given the errors, the cost associated with the errors, the prevention and
the cost associated with the preventing them, you can make an engineering
or business decision.

53:50 Even constraining values may lead to a false sense of of security. For
example, on the Lonely Planet web site June 31 was possible!

54:05 Consistency: two different methods for date specification on the Lonely
Planet. Bad for muscle memory!

54:53 Avoid over reliance on string. String is known as a type sink!

56:07 Different types facilitate type-specific type formatting and validation
code!

56:19 Rather than using strings in your API's, you should be using something
just descriptive about what they stand for.

57:28 Starts to answer the questions.

Bjarne Stroustrup - Writing Good C++14 @ CppCon 2015, 21 September 2015

2016-01-05T15:12:00.002+02:00

For the 101 minutes video: https://www.youtube.com/watch?v=1OEu9C51K2A

For the C++ Core Gudilelines: https://github.com/isocpp/CppCoreGuidelines

For the Microsoft GSL: https://github.com/isocpp/CppCoreGuidelines

Bjarne Stroustrup talks basically on the Guidelines Support Library (GSL). I took the following notes while watching the excellent talk:

02:55 Very few people write modern C++ code.

03:36

04:40 Inventing a new language in order get a better and simpler
one is a bad idea!

08:50 We don't like coding rules. They are aimed to prevent
accidents: basically "don't do" lists. Not aimed for quality
code.

09:50 Coding rules recommends restrictions on C++ features.

10:00 There are a lot of bad advice!

11:58

12:07 I don't understand the MISRA C++ pointer rules: they are
miserable!

17:56 Language subsetting doesn't work.

18:15 Write high-level code via libraries using all the language
features.

19:10 After you build the superset, i.e. language + libraries, you
subset.

19:30 What we want is "C++ on steroids".

23:40 Tool support, i.e. static analysis, is essential.

25:10 No resource leaks: RAII, i.e. no naked new and delete!

32:50 GSL: owner is for fixing the dangling pointer nightmare.

33:15 Owner is intended to simplify static analysis.

37:00 Besides dangling pointers, there are other pointer misuses:
range errors: fix it with array_view.
nullptr dereferencing: fix it with non_null.

37:18 We want to minimize run-time checks, because we want to run
fast!

37:50 My least favorite interface:
void f(int *p, int n);
why?
So common!
So error-prone!
Fix it with array_view.

40:15 nullptr problems: fix it with not_null.

41:30 not_null is for minimising run-time checking!

42:20 "Smart pointers" are overused to overcome ownership and
dangling pointer problems.

43:12 As the dangling pointers are eliminated by tools, you don't
need to use them!

47:30 Too many rules: the tools should know the rules and will
point you the relevant ones.

49:15 There are too many rules and it doesn't work me! I want lots
of rules.

50:00 I hate camel case.

51:20 We aren't unambitious:
Aim type and resource safety.
Consider all 4+ millions C++ programmers.
Zero-overhead principle.

51:50 We aim to change the way we write code.

53:52 Help wanted! There are currently only two editors: me and
Herb Sutter.

55:02 The basic C++ model is now complete.

57:20 Starts to answer the questions.

Summary of JSF Air Vehicle C++ Coding Standards

2015-09-12T11:29:00.000+03:00

See http://www.stroustrup.com/JSF-AV-rules.pdf

JOINT STRIKE FIGHTER
AIR VEHICLE
C++ CODING STANDARDS
FOR THE SYSTEM DEVELOPMENT AND DEMONSTRATION PROGRAM Document Number 2RDU00001 Rev C

December 2005

Copyright 2005 by Lockheed Martin Corporation.
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

1 INTRODUCTION

The intent of this document is to provide direction and guidance to C++ programmers that will enable them to employ good programming style and proven programming practices leading to safe, reliable, testable, and maintainable code... As indicated above, portions of Air Vehicle (AV) code will be developed in C++... Overall, the philosophy embodied by the rule set is essentially an extension of C++’s philosophy with respect to C. That is, by providing “safer” alternatives to “unsafe” facilities, known problems with low-level features are avoided.

2 REFERENCED DOCUMENTS

3 GENERAL DESIGN

3.1 Coupling & Cohesion

Coupling and cohesion are properties of a system that has been decomposed into modules. Cohesion is a measure of how well the parts in the same module fit together. Coupling is a measure of the amount of interaction between the different modules in a system. Thus, cohesion deals with the elements within a module (how well-suited elements are to be part of the same module) while coupling deals with the relationships among modules (how tightly modules are glued together).

Object-oriented design and implementation generally support desirable coupling and cohesion characteristics. The design principles behind OO techniques lead to data cohesion within modules. Clean interfaces between modules enable the modules to be loosely coupled. Moreover, data encapsulation and data protection mechanisms provide a means to help enforce the coupling and cohesion goals.

Source code should be developed as a set of modules as loosely coupled as is reasonably feasible. Note that generic programming (which requires the use of templates) allows source code to be written with loose coupling and without runtime overhead.

Examples of tightly coupled software would include the following:
• many functions tied closely to hardware or other external software sources, and
• many functions accessing global data.
There may be times where tightly coupled software is unavoidable, but its use should be both minimized and localized as suggested by the following guidelines:
• limit hardware and external software interfaces to a small number of functions,
• minimize the use of global data, and
• minimize the exposure of implementation details.

3.2 Code Size and Complexity

AV Rule 1
Any one function (or method) will contain no more than 200 logical source lines of code (L- SLOCs).
Rationale: Long functions tend to be complex and therefore difficult to comprehend and test.

AV Rule 3
All functions shall have a cyclomatic complexity number of 20 or less.
Rationale: Limit function complexity.

4 C++ CODING STANDARDS

4.6 Pre-Processing Directives

AV Rule 28
The #ifndef and #endif pre-processor directives will only be used as defined in AV Rule 27 to prevent multiple inclusions of the same header file.
Rationale: Conditional code compilation should be kept to a minimum as it can significantly obscure testing and maintenance efforts.

4.9 Style

AV Rule 41
Source lines will be kept to a length of 120 characters or less.
Rationale: Readability and style. Very long source lines can be difficult to read and understand.

AV Rule 49
All acronyms in an identifier will be composed of uppercase letters.
Note: An acronym will always be in upper case, even if the acronym is located in a portion of an identifier that is specified to be lower case by other rules.
Rationale: Readability.

4.9.4 Functions

AV Rule 58
When declaring and defining functions with more than two parameters, the leading parenthesis and the first argument will be written on the same line as the function name. Each additional argument will be written on a separate line (with the closing parenthesis directly after the last argument).

Rationale: Readability and style.

4.9.5 Blocks

AV Rule 59 (MISRA Rule 59, Revised)
The statements forming the body of an if, else if, else, while, do...while or for statement shall always be enclosed in braces, even if the braces form an empty block.
Rationale: Readability. It can be difficult to see “;” when it appears by itself.

4.9.6 Pointers and References

AV Rule 62
The dereference operator ‘*’ and the address-of operator ‘&’ will be directly connected with the type-specifier.
Rationale: The int32* p;form emphasizes type over syntax while the int32 *p; form emphasizes syntax over type. Although both forms are equally valid C++, the heavy emphasis on types in C++ suggests that int32* p; is the preferable form.

4.10 Classes

4.10.3 Member Functions

AV Rule 68
Unneeded implicitly generated member functions shall be explicitly disallowed. See Meyers [6], item 27.
Rationale: Eliminate any surprises that may occur as a result of compiler generated functions. For example, if the assignment operator is unneeded for a particular class, then it should be declared private (and not defined). Any attempt to invoke the operator will result in a compile-time error. On the contrary, if the assignment operator is not declared, then when it is invoked, a compiler-generated form will be created and subsequently executed. This could lead to unexpected results.
Note: If the copy constructor is explicitly disallowed, the assignment operator should be as well.

4.13 Functions
4.13.1 Function Declaration, Definition and Arguments

AV Rule 110
Functions with more than 7 arguments will not be used.
Rationale: Functions having long argument lists can be difficult to read, use, and maintain. Functions with too many parameters may indicate an under use of objects and abstractions.
Exception: Some constructors may require more than 7 arguments. However, one should consider if abstractions are being underused in this scenario.

AV Rule 112
Function return values should not obscure resource ownership.

Rationale: Potential source of resource leaks.

4.13.2 Return Types and Values

AV Rule 113 (MISRA Rule 82, Revised)
Functions will have a single exit point.
Rationale: Numerous exit points tend to produce functions that are both difficult to understand and analyze.
Exception: A single exit is not required if such a structure would obscure or otherwise significantly complicate (such as the introduction of additional variables) a function’s control logic. Note that the usual resource clean-up must be managed at all exit points.

AV Rule 122
Trivial accessor and mutator functions should be inlined.
Rationale: Inlining short, simple functions can save both time and space.

4.15 Declarations and Definitions

AV Rule 137 (MISRA Rule 23)
All declarations at file scope should be static where possible.

4.16 Initialization

AV Rule 142 (MISRA Rule 30, Revised)
All variables shall be initialized before use.
Rationale: Prevent the use of variables before they have been properly initialized.
Exception: Exceptions are allowed where a name must be introduced before it can be initialized (e.g. value received via an input stream).

AV Rule 143
Variables will not be introduced until they can be initialized with meaningful values.
Rationale: Prevent clients from accessing variables without meaningful values.

4.17 Types

AV Rule 148
Enumeration types shall be used instead of integer types (and constants) to select from a limited series of choices.
Note: This rule is not intended to exclude character constants (e.g. ‘A’, ‘B’, ‘C’, etc.) from use as case labels.
Rationale: Enhances debugging, readability and maintenance. Note that a compiler flag (if available) should be set to generate a warning if all enumerators are not present in a switch statement.

4.19 Variables

AV Rule 152
Multiple variable declarations shall not be allowed on the same line.
Rationale: Increases readability and prevents confusion.

4.21 Operators

AV Rule 162
Signed and unsigned values shall not be mixed in arithmetic or comparison operations.
Rationale: Mixing signed and unsigned values is error prone as it subjects operations to numerous arithmetic conversion and integral promotion rules.

AV Rule 163
Unsigned arithmetic shall not be used.
Rationale: Over time, unsigned values will likely be mixed with signed values thus violating AV Rule 162.

4.22 Pointers & References

AV Rule 175
A pointer shall not be compared to NULL or be assigned NULL; use plain 0 instead.
Rationale: The NULL macro is an implementation-defined C++ null pointer constant that has been defined in multiple ways including 0, 0L, and (void*)0. Due to C++’s stronger type-checking, Stroustrup [2] advises the use plain 0 rather than any suggested NULL macro.

4.24 Flow Control Structures

AV Rule 189 (MISRA Rule 56)
The goto statement shall not be used.
Rationale: Frequent use of the goto statement tends to lead to code that is both dif read and maintain.
Exception: A goto may be used to break out of multiple nested loops provided the alternative would obscure or otherwise significantly complicate the control logic.

AV Rule 190 (MISRA Rule 57)
The continue statement shall not be used.

AV Rule 191 (MISRA Rule 58)
The break statement shall not be used (except to terminate the cases of a switch statement).
Exception: The break statement may be used to “break” out of a single loop provided the alternative would obscure or otherwise significantly complicate the control logic.

AV Rule 200
Null initialize or increment expressions in for loops will not be used; a while loop will be used instead.
Rationale: A while loop provides a more natural representation.

4.26 Memory Allocation

AV Rule 206 (MISRA Rule 118, Revised)
Allocation/deallocation from/to the free store (heap) shall not occur after initialization. Note that the “placement” operator new(), although not technically dynamic memory, may only be used in low-level memory management routines.
Rationale: Repeated allocation (new/malloc) and deallocation (delete/free) from the free store/heap can result in free store/heap fragmentation and hence non-deterministic delays in free store/heap access.

4.28 Portable Code

4.28.5 Pointer Arithmetic

AV Rule 215 (MISRA Rule 101)
Pointer arithmetic will not be used.

4.29 Efficiency Considerations

AV Rule 216
Programmers should not attempt to prematurely optimize code. See Meyers [7], item 16.
Rationale: Early focus on optimization can result in sacrificing the clarity and generality of modules that will not be the true bottlenecks in the final system.
Premature optimization is the root of all evil – Donald Knuth
Note: This rule does not preclude early consideration of fundamental algorithmic and data structure efficiencies.

A Macro to Dump CGRect

2014-08-29T16:21:00.005+03:00

Recently, I worked on a class derived from UIScrollView. In order to dump the CGRect's conveniently, I mean better than NSStringFromCGRect(), I introduced the following macro:

#ifdef DEBUG

#define DBG(format, ...) NSLog(@"%d,%s,"format,__LINE__,__FUNCTION__,##__VA_ARGS__);

#define DUMP_RECT(rect) DBG("\n" \

#rect"\n" \

"....x:|%.0f|\n" \

"....y:|%.0f|\n" \

"....width:|%.0f|\n" \

"....height:|%.0f|\n", \

rect.origin.x, \

rect.origin.y, \

rect.size.width, \

rect.size.height)

#else

#define DBG(format, ...)

#define DUMP_RECT(rect)

#endif

Note the stringizing operator (#) operator to dump the "rect". Its sample use in LPTSCrollView class:

- (void)reset

{

...

DUMP_RECT(self.frame)

DUMP_RECT(self.bounds)

...

}

Its sample outputs:

2014-08-29 16:15:03.829 PhotonPro[18253:60b] 98,-[LPTScrollView reset],

self.frame

....x:|0|

....y:|0|

....width:|320|

....height:|568|

2014-08-29 16:15:03.830 PhotonPro[18253:60b] 100,-[LPTScrollView reset],

self.bounds

....x:|0|

....y:|0|

....width:|320|

....height:|568|

Hopefully, it will help somebody!

Guardians of Dawn (1963)

2013-05-16T01:01:00.005+03:00

2013 is the 50th anniversary of the famous Turkish movie Guardians of Dawn ("Şafak Bekçileri") [1] directed by late Halit Refiğ who also wrote the scenario. It was shot black and white in location, at the Eskişehir Air Force Base in 1963. The producer of the movie is Göksel Arsoy who originated the idea and played the lead character. The Turkish moviegoers watched the noisy and powerful military jets on the white screen for the first time and the movie proved to be wildly popular when released. In order to help non-Turkish speaking audience, I created English subtitles of the movie in the SRT format which can be freely downloaded and distributed [2].

Theatrical release poster

A T-33A lands while the Turkish title of the movie is displayed. It is a befitting gesture as two T-33A's were the very first jet aircraft of the TuAF in 1951.

(Still frame from the movie @ 00 min 02 sec)

Director: Halit Refiğ.
(Still frame from the movie @ 02 min 11 sec)

Scenario: Halit Refiğ with Sadık Şendil and Bülent Oran
1st Lt Akinci is in the cockpit of his F-100D under the watchful eyes of Master Sergeant Karadayi.

(Still frame from the movie @ 01 min 21 sec)

Producer: Göksel Arsoy
Note that two F-100D's are taking off.

(Still frame from the movie @ 02 min 01 sec)

Among the players listed: 1st Air Force Officers, NCO's and Enlisted Soldiers.
1st Lt Akinci is climbing the ladder to his F-100D's cockpit while Master Sergeant Karadayi is holding his flight helmet.

(Still frame from the movie @ 01 min 02 sec)

Background

The movie tells the story of progressive aviators against a reactionary local Agha behind the romance of a young Turkish Air Force [4] jet pilot and the Agha's beautiful daughter. As the movie was shot after the military coup d'état on 27 May 1960 which was supported by some left wing intellectuals including Halit Refiğ [5], the movie presents the Turkish military officers as progressive leaders struggling against the local reactionary leaders. In some sense, even the title of the movie hints its wisdom: the future ("dawn") of Turkey was guarded by her military. Halit Refiğ says "In fact, Guardians of Dawn is a defense of the 1960 coup d'état. It isn't just a movie about the jet pilots. Of course, this is the basic story, but in the background the movie is about the decisive role of the Military on the Turkish society... In 1963 I didn't know the intricacies of the 27 May [coup d'état] and I was fully supporting it." [6] Note that Halit Refiğ changed his position on the 1960 coup d'état and the Turkish Military by the late 1960's partly due to strong influence of Kemal Tahir [7].

The director Halit Refiğ's two movies Abroad Birds ("Gurbet Kuşları", 1964) and Guardians of Dawn ("Şafak Bekçileri", 1963) in the Şan Theater together in 1965 [3].

Production

The director Halit Refiğ is on the foreground during the shooting [8]. At the background 113 "Pirate" Squadron F-100D 54-2228 which was received on 13 May 1959 is visible [9].

The idea behind the movie belongs to Göksel Arsoy who has interested in aviation since his childhood and his father was a civilian engineer at Kayseri Air Force Base. In Turkish "Göksel" means heavenly and according to Halit Refiğ [10] he was so named because his father liked aircraft and befriended a lot of pilots. Plus, the father of Göksel Arsoy's wife was a retired general who was a close friend of the then C-in-C of the Turkish Air Force General Irfan Tansel. Göksel Arsoy asked for permission from the TuAF for a movie and he got the official approval [11]. Halit Refiğ believed that the movie materialized only due to Göksel Arsoy and his connections [12].

The above scene in the movie: F-100D 54-2228 is being towed in the background while pilots who will take part in the air show walk to their aircraft including 1st Lt Akinci (Göksel Arsoy) and 1st Lt Faruk (Ekrem Bora). Note that the 114 "Light" Squadron Commander Major Ilhan Sonüstün [13] is on the foreground.
(Still frame from the movie @ 55 min 24 sec)

Previously, Halit Refiğ worked with Göksel Arsoy in two movies and Göksel Arsoy offered him to direct his new movie project. He accepted with some reservations: "Interesting idea. But I know nothing about aircraft First I need to know them" [14]. Both of them visited the Eskisehir Air Force Base several months before shooting the move and flew with jets thanks to a special permission [15]. The TuAF helped the movie shooting considerably: a many TuAF officers took part in the movie, for example Major İlhan Sonüstün and 1st Lt Güner Kurtuluş, and one of them, Ahmet Çörekçi, later became the C-in-C of the TuAF [16].

1st Lt Güner Kurtuluş asks which school he will guide. 1st Lt Faruk (Ekrem Bora) jokes that it is a Girls High-school. At that time he was assigned to the 114 "Light" Reconnaissance Squadron.

(Still frame from the movie @ 25 min 09 sec)

The scenario originally was written by Sadik Şendil and heavily emphasized romance. However, Halit Refiğ got Göksel Arsoy's approval for a "more realistic" scenario [17]. He decided to emphasize the pilot psychology and the pioneer role of the Turkish Military in introducing modernity and technological innovations [18]. He said "Unavoidably, I needed to specify my position on the 27 May [coup d'état]. Considering the ideas I upheld then, I decided to specifically emphasize the modernizing character of the Turkish Armed Forces. Jet aircraft gave me the opportunity." [19]

The C-in-C of the Turkish Air Force General Irfan Tansel fully supported the movie. 1st Air Force commander General Muhsin Batur liked Halit Refiğ and did hist best during the production.

When Göksel Arsoy screened the movie on 30 August 1963 [20] in Izmir outdoor movie theater, the censorship authorities stopped it after 10 minutes because in the movie there were aircraft crashes and Göksel Arsoy kissed his sweetheart while he wore a uniform. Then, Göksel Arsoy invited Gen. Irfan Tansel and other high-ranking officers along with their wifes to the studio in which the movie was processed in Istanbul and arranged a special screening. As Gen. Irfan Tansel liked the movie very much the ban on the movie was lifted within two days [21].

When released to the theaters, the movie was liked widely and attracted much attention. It collected a record grossing and encouraged a record number of youngsters to apply for the Air War Academy [22].

Characters

1st Lt Akinci
(Göksel Arsoy)

1st Lt Göksel Akinci: (Göksel Arsoy) A Turkish Air Force jet pilot. He is a very capable and idealist aviator loving his profession very much. He falls in love with Zeynep unknowing that she is the daughter of villain Kudret Agha. His love of Zeynep and aviation clashes as both Zeynep and Kudret Agha pressure him to resign his commission immediately. He urges Zeynep to care for the poor people living on their farm and nearby villages.

Zeynep
(Leyla Sayar)

Zeynep: (Leyla Sayar) Beautiful daughter of Kudret Agha. She completes her education in Istanbul and returns her hometown Eskisehir to marry with "Cowboy" Kerim. The marriage is prearranged between her father and Emrullah Bey. She was indifferent to the plight of poor peasant working in his father's farm leaving such "business" issues to her father until she falls in love with 1st Lt Akinci.

1st Lt Faruk(Ekrem Bora)

1st Lt Faruk: (Ekrem Bora) A Turkish Air Force jet pilot. The closest friend of 1st lt Akinci. After his parents divorced, he was raised by his uncle in poverty. He is a humorous and tough aviator who is always ready chase women. His death in a flying accident devastates 1st Lt Akinci. He buzzes Kudret Aga as much as possible.

Kudret Agha
(Mümtaz Ener)

Kudret Agha: (Mümtaz Ener) The arch villain, an Agha. "Kudret" means "power" in Turkish. He is a very wealthy and ruthless man. He believes that every man fulfills his fate and openly exploits the poor peasants. For him poverty and hardships should be shouldered as fate. He shows no mercy for his workers to keep a very rigid discipline. He opposes better living standards and education for the peasants to keep the status quo. Consequently, he disapproves any change and hates the reformist people like Teacher Ihsan.

Emrullah Bey

Emrullah Bey: A prominent local right wing politician, a Bey. "Emrullah" means "God's order" in Arabic. He collaborates closely with Kudret Agha. He fixes the problems faced by Kudret Aga "democratically", i.e. in the capital Ankara using his political connections. He and Kudret Agha agreed to have their children Zeynep and "Cowboy" Kerim married.

Lt Aydan
(Nilüfer Aydan)

Lt Aydan: (Nilüfer Aydan) A Turkish Air Force female officer. She always advises her male colleagues for their love affairs. She loves 1st Lt Akinci, but somehow she never attracts his attention. She is the daughter of Master Sergeant Karadayi.

Cowboy Kerim
(Oktay Menteş)

"Cowboy" Kerim: (Oktay Mentes) This villain is the unsophisticated son of Emrullah Bey. He is engaged with Zeynep to cement the close relationship between his father and Kudret Agha. He wastes his time with card playing etc. and leads a group of thugs.

Teacher Ihsan

"Teacher" Ihsan: An idealist teacher. He teaches the illiterate conscripts like Memo. He always tries to "enlighten" people and talks about "national development problems".

"Fram Manager" Hamdi
(Hüseyin Baradan)

"Farm Manager" Hamdi: (Hüseyin Baradan) This villain works in Kudret Agha's farm. He is a very rude and unrefined man. When fired by Kudret Agha, he decides to revenge which proves to be a fatal mistake.

Master Sergeant Karadayi
(Ahmet Tarik Tekce)

Master Sergeant Karadayi: (Ahmet Tarık Tekçe) A Turkish Air Force maintenance NCO. He is very dedicated to aircraft in his care. He loves aviation very much despite having lost his jet pilot son in a flying accident. He is the father of Lt Aydan.

Memo
(Sami Hazinses)

Memo: (Sami Hazinses) An illiterate conscript from rural Turkey. He believes in the crude legends about a local Sheikh. He symbolizes the uneducated, naive and congenial ordinary Turkish citizens. He is being taught how to read and write by Teacher Ihsan in a class supervised by the military which is an example how the military tries to open the eyes of uneducated citizens.

Critique

The political wisdom of the movie is outside the scope of this article. I enjoy it as an aviation movie shot in 1960s Turkey showing the legendary "Papa" Super Sabre in the TuAF service.

Arguably the best aerial Super Sabre footage in the movie. Ex-USAF F-100D 55-2754 of 113 "Pirate" Sqn and Ex-USAF F-100D 54-2218 of 111 "Panther" Sqn flies together. At that time all the Super Sabre squadrons enjoyed magnificent insignia on their mounts. Note that the shot lasts only a few seconds! They were received on 9 Jan 1958 and 29 May 1959 respectively [23]. F-100D 54-2218 written off on 21 Feb 1972 [24].
(Still frame from the movie @ 2 min 41 sec)

I think the movie is showing the TuAF aircraft less than expected from an aviation movie, for example there is no close shot of jets breaking formation. Overall, there are very few air-to-air scenes. The aircraft just provides an impressive background for the story. If one compares it with a magnificent aviation movie like The Bridges at Toko-Ri (1954), the Guardians of Dawn fares definitely badly. Apparently Halit Refiğ decided that a few seconds presence of the jets would awe the audience, he focused always the actors and never bothered to film the then expensive and modern Super Sabre's in detail. That being said, it is an excellent first aviation movie for the Turkish cinema.

1st Lt Faruk during his ill-fated T-33A flight. Note that the clouds stay stationary and obviously the scene shot on the ground.

(Still frame from the movie @ 87 min 17 sec)

Considering the political climate of the era, 1st Lt Akinci challenges Kudret Aga for his fanatical disregard of the poor peasants. He sincerely urges Zeynep to care for them disregarding his father and so-called traditions. I guess if the movie had shot in the modern times, the only tension would have arose from the aviation enthusiasm of the 1st Lt Akinci as he resists the pressure coming from Zeynep and Kudret Aga to resign from the TuAF. The movie shows a long-forgotten, but honorable emphasize on the social equality and far away from the individualist climate of the modern times.

Zeynep brings 1st Lt Akinci to her nearby home to care his scratches. Note the 113 "Pirate" Sqn badge on Göksel Arsoy's chest.

(Still frame from the movie @ 43 min 38 sec)

The movie is very verbose and action scenes are rare. Specifically, the final mission of the 1st Akinci was filmed very poorly: we watch an F-100D/F take off scene and a low flying Super Sabre. Then, we learn what did happen from a Major's report to the General. I think it is too theatrical! Between the two scenes, the focus is on Zeynep and Lt Aydan.

A Major reports the fate of 1st Lt Akinci to the General. Note the 113 "Pirate" Sqn badge on his flying suit. At that time the flight cap was not in use and the officer wore a regular hat.

(Still frame from the movie @ 111 min 45 sec)

I think the dangerous reconnaissance mission assigned to the 1st Lt Akinci is due fact that the movie shot in the 114 "Light" Recce Sqn premises. I assume naturally its officers suggested such a mission for the plot. However, I think the mission ended in utter failure as the aircraft shot down and consequently the films are lost. Plus, the mission is an odd assignment as the reconnaissance isn't a Super Sabre mission in the TuAF service [25], but a specialty of the RF-84F Thunderflashes equipping the 114 Sqn.

The eulogy during 1st Lt Faruk's funeral despite poorly recorded, see 89th minute, and afterwards a very sorrow 1st Lt Akinci's heart-breaking comments on the lost fliers before their photographs to Zeynep, see 91st minute, are both emotional and powerful scenes. In the later scene I guess Göksel Arsoy know many of the deceased by himself.

A very sorrow 1st Lt Akinci tells the stories of the deceased pilots to Zeynep after attending 1st Lt Faruk's funeral.

(Still frame from the movie @ 91 min 47 sec)

Among the characters in the movie, I think Kudret Aga played by late Mümtaz Ener and 1st Lt Faruk played by late Ekrem Bora stands out. Sami Hazinses plays his role Memo wonderfully just like Ahmet Tarik Tekce and Hüseyin Baradan. I think Leyla Sayar plays her role as Zeynep a bit sleepy and tired. I don't know who played "Teacher" Ihsan but I think he looks to be very boring in his narrow suits. Finally, the "Cowboy" Kerim character is not persuasive at all: he looks to be an ordinary local thug, not the son of a prominent local politician.

Arguably no TuAF front line squadron has painted their mounts more enthusiastically then its early 1960s Super Sabre squadrons. They introduced well designed flamboyant squadron insignia. I think even the contemporary TuAF squadron insignia aren't up to the quality of them. It is a pity that the most flamboyant period of the TuAF wasn't recorded in color!

Overall, the Guardians of Dawn is a very nice Turkish movie of the early 1960s and I guess all the Turkish military aviation enthusiasts owe gratitude to both late Halit Refiğ and Göksel Arsoy for it. Thank you!

Aircraft

Note that all the aircraft types recorded in the movie are phased out of service. The last one of the movie types to retire is the C-47's which retired in 1998.

North American F-100 Super Sabre

F-100D 54-2201 was received on 31 October 1958, here painted in 113 "Pirate" Squadron colors
(Still frame from the movie @ 102 min 48 sec)

In 1958 the TuAF received its first North American F-100D/F Super Sabre jets. Then, the Super Sabre was a record breaking very capable jet aircraft introduced to USAF service in 1954. Around 267 aircraft received over the years from multiple sources [26]. Note that the earlier F-100C model was received by the TuAF later than F-100D/F models in 1972 when they are retired from the Air National Guard service after serving in Vietnam [27].

As it a complex and demanding aircraft, the TuAF assigned its best aviators to its F-100's squadrons [28]. Both the 111 and 113 Squadrons were tasked with nuclear strike by NATO armed with the USAF controlled nuclear bombs between 1963-1974 [29]. The Super Sabre was much liked by its Turkish service men: it was nicknamed "baba" (Papa) being a very tough aircraft [30]. The proud F-100 Squadrons painted over their aircraft flamboyant squadron insignia which has never seen again over the TuAF aircraft [31].

On 1 June 1962, during the TuAF's 51th anniversary day celebrations, Ex-USAF F-100D 54-2743 crashed directly over the audience resulting in 5 fatalities including the pilot and 41 injuries [32]. Due to this disaster, public aerobatic flights was forbidden for decades by the TuAF. The NATO competition Best Hit 1971 was hosted by TuAF in the Eskişehir Air Base and won by its 111 Sqn F-100D's [33]. The F-100's were much used in action in 1964 and 1974 over Cyprus: on 8 August 1964 Capt Cengiz Topel of 112 Squadron was shot down by the Cypriot Greeks while flying Ex-USAF F-100D 55-2766 and although ejected safely, he was captured and killed [34]. On 22 July 1974 the Super Sabres attacked along with F-104G's and sunk Turkish Navy's TCG Kocatepe destroyer in a friendly-fire incident. On 14 Sep 1983 Ex-USAF F-100F 56-903 which was received on 8 Feb 1972 accidentally violated the Iraqi border and was shot down by an Iraqi Mirage F-1EQ [35]. When the beloved F-100's was phased out of service in 1988 Turkish Air Force was the last operator.

In the movie, it is the principal jet flown by 1st Lt Akinci: he crash lands an F-100D at the beginning, see 4th min, and survives an F-100D ejection near the end, see 111th min.

The Super Sabre was replaced with F-4E Phantom.

F-100D 55-2766 of Capt Cengiz Topel, 112 "Devil" Squadron

(1/32 model by Özkan Türker)

Ex-USAF F-100D 54-2173 was received on 12 November 1958. 113 "Pirate" Sqn was transferred to Erhaç Air Force Base and renumbered as 171 Sqn in 1967. The squadron insignia was designed by 1st Lt Nural Varal [36]. Note that the yellow boomerang on the tail doesn't conform to the period photos [37] and the 113 Sqn Super Sabres shot in the movie. Today, this squadron flies the with modernized F-4E 2020's.
(tayyareci.com)

Ex-USAF F-100D 55-2754 was received on 09 January 1958. 111 "Panther" Sqn is the first F-100 squadron of the TuAF. Apparently, this aircraft flew with the 113 "Pirate" Sqn, see the 2nd min in the movie. Today, this squadron flies with the modernized F-4E 2020's.(tayyareci.com)

Ex-USAF F-100F 56-3946 of 111 "Panther" Squadron, June 1971, Eskisehir. Note that by this time flamboyant squadron insignia removed and USAF SEA style camouflage applied. Currently, this aircraft is preserved in Eskisehir [38].

The same F-100F 56-3946 which was assigned to 112 "Devil" Squadron was photographed during a squadron exchange on 11 September 1973 in Norvenich, Germany. Note that the aircraft sports the current TuAF insignia. The extreme heat around the afterburner burned the aft fuselage paint which was very common [39].

(Photo by Günter Grondstein, Airliners.net)

F-100D 56-3399 of 111 "Pirate" Squadron sporting the old "square" TuAF insignia in the USAF SEA camouflage. This aircraft crashed on 24 September 1974 due to engine failure. Note the absence of squadron insignia.

(Photo by Firuz Altıngöz)

Lockheed T-33 Shooting Star

Ex-USAF T-33A 53-5791 was received in July 1955 and withdrawn from use on 11 March 1996. This aircraft has survived its ordeal and currently preserved in Diyarbakir [47].

(Still frame from the movie @ 26 min 13 sec)

T-33A is the aircraft opening the movie. Around 193 aircraft received over the years from multiple sources [48]. They were used between 1951-1994 for reconnaissance, liaison and training. 1st Lt Güner Kurtuluş flown Göksel Arsoy in a T-33A on 26 March 1963 [49]. The aircraft was Ex-USAF 53-5743 which was received on 21 June 1955 [50]. In the movie, 1st Lt Faruk dies in a T-33A accident after buzzing Kudret Agha in a daring low-level flying, see 87th min.

1st Lt Faruk buzzes Kudret Aga with a T-33A.

(Still frame from the movie @ 87 min 06 sec)

This ex-USAF Lockheed T-33A 53-5744 was received on 21 June 1955 [51] and is now displayed in the Turkish Air Force Museum in Istanbul

(Photo by Peter de Jong on 30 July 2006, Airliners.net)

Republic RF-84F Thunderstreak

Ex USAF RF-84F 52-8760 with Zeynep and Lt Aydan which was received on 10 July 1957 [43]. Note the 114 "Light" Sqn insignia on the nose.

(Still frame from the movie @ 115 min 10 sec)

The movie was shot in 114 Sqn premises which was equipped with Republic RF-84F Thunderstreak reconnaissance jets. In the movie, the crashed jet of 1st Lt Akinci is found by RF-84F's. Around 80 aircraft received over the years from multiple sources [44]. They were used between 1959-1980 for reconnaissance and replaced with RF-4E phantom.

This ex-USAF Republic RF-84F 52-7450 was received on 19 September 1956 [45]. Note the 114 "Light" Sqn insignia on the nose.
(Official TuAF photo)

This ex-USAF Republic RF-84F 51-1901 was received on 25 February 1958 [46] and is now displayed in the Turkish Air Force Museum in Istanbul

(Photo by Peter de Jong on 30 July 2006, Airliners.net)

North American F-86E(M) Sabre (Canadair CL-13 Mk.2)

Ex Canadian F-86E(M) 19247 was received on 16 July 1955 [40].

(Still frame from the movie @ 56 min 06 sec)

The Sabre is a much loved aircraft in the Turkish Air Force service [41]. It was used between 1954-1968 and replaced by Northrop F-5A/B. However, in the movie it was shown briefly.

This ex-Canadian Canadair CL-13 Mk.2 19207 was received on 16 July 1955 [42] and now displayed in the Turkish Air Force Museum in Istanbul.(Photo by Peter de Jong on 30 July 2006, Airliners.net)

Douglas C-47 Dakota

A C-47 takes off with 1st Lt Akinci and 1st Lt Lt Faruk.

(Still frame from the movie @ 09 min 35 sec)

A true legend, the DC-3 airliner first flown in 1935. Its military version C-47 first flown in 1941 and its turboprop conversions are still in military service [52]. Around 110 C-47A/B and DC-3 were received over the years from multiple sources [53]. They were used between 1948-1998 for transportation. In the movie, Lt Akinci and Lt Faruk go to Istanbul with a C-47, see 9th min and jumps from a C-47 for training the conscripts and by chance meets with Zeynep, see 40th min. It was replaced with CN-235.

A TuAF C-47 drops parachutist. Note the worn out air force insignia on the aft body.

(Official TuAF photo)

Beechcraft AT-11 Kansan

An AT-11 piloted by 1st Lt Faruk drops the squadron's gift.

(Still frame from the movie @ 74 min 12 sec)

This light weight, twin engine aircraft were used for liaison and training. Around 128 ex-USAF aircraft were received between 1948-1983 [54]. In the movie, an AT-11 piloted by 1st Lt Faruk drops the squadron's gift to 1st Lt Akinci after his engagement, see 74th min.

A TuAF AT-11 Kansan.

(28, Photo by Firuz Altıngöz, July 1975)

Sikorsy UH-19B/D Chickasaw

UH-19D 56-4271 [55] takes off to rescue 1st Lt Akinci.

(Still frame from the movie @ 111 min 36 sec)

The Chickasaw was the first helicopter entering the TuAF service. Between 1958 and 1980 around 18 ex-USAF/US Army examples were used [56]. In the movie, it is used to bring the 1st Lt Akinci home, see 111th min.

UH-19B

(52-7543, Photo by Firuz Altıngöz, August 1976)

Turkish Air Force Insignia

The TuAF used "square" insignia until 1972. It was a red square outlined in white. Then, it was replaced with "red-white-red roundel" which is currently in use. The change is due to fact that high aircraft speeds it is possible to confuse the red square with the Soviet Air Force's red star marking. The national flag is painted on the fin [57] which is reduced in size since the 1970s. Consequently, in the movie all the TuAF aircraft is seen with red squares outlined in white with the Turkish flags on their tails.

Ex-USAF F-102A 55-3413 landing at Mürted Air Force Base circa 1972. It was received on 29 August 1968 and crash landed to a road on 22 July 1974 after intercepting Greek F-5A's due to fuel starvation. The TuAF used T/F-102A's between 1968 and 1979 [58].

(Photo by Emin Findikli)

171 "Pirate" Squadron's modernized F-4E 2020 Terminator takes off in Lechfeld, Germany. Note the artwork on the tail which apparently based on Ottoman naval soldiers called Levent.

(Photo by Daniel Obers on 24 June 2010, Airliners.net)

Trivia

The director Halit Refiğ married with Nilufer Aydan on 24 February 1962 [59] [60]. The marriage lasted for two years. So, while the movie shot they were a married couple.

The director Halit Refiğ's Abroad Birds ("Gurbet Kuşlari", 1964) movie is the first movie of Cüneyt Arkin who was serving in the Eskisehir Air Force Base as a doctor doing his national service while the movie was shot. He attracted much attention from the movie crew, including Halit Refiğ and Leyla Sayar, but he didn't took part in the movie. After completing his national service, he started his movie career by asking for a role from Halit Refiğ [61].

Late Necdet Tosun plays his characteristic cook role in the movie, see 33rd min.

The current Turkish Air Force insignia, i.e. red-white-red roundel, is exactly the same as Peruvian Air Force insignia.

Apparently, the Turkish Air Force had some beard-wearing officers and NCO's in the early 1960s. Today, it is forbidden for the members of the Turkish Armed Force to wear beard.

In the movie, the airmen address each other with their ranks. Today, junior airmen address the senior ones with "Sir". In fact, the exact translation is "my commander". Perhaps the change is due to influence of the Turkish Army.

When the movie was shot, Eskisehir Air Force Base was part of 1st Air Force [62]. It later renamed 1st tactical Air Force à la USAF's Tactical Air Command. However, the USAF dissolved the Tactical Air Command and both of the operational commands of the TuAF have the word "tactical" dropped in their names.

Bibliography

Halit Refiğ Düşlerden Düşüncelere Söyleşiler, Ibrahim Türk, Kabalci Yayinevi, 2001, Istanbul

F-100 Super Sabre in Turkish Air Force, Volume 1, Levent Başara, HobbyTime, 2011, Ankara

Notes

[1] See the movie at IMDB and Turkish Wikipedia.

[2] Guadians of Dawn (Safak Bekcileri, 1963) by Oguz Kupusoglu.srt

[3] Ibrahim Turk, p149.

[4] For the modern Order of battle of the Turkish Air Force, see the Scramble article.

[5] Ibrahim Turk, p127. For a late 1960's example see Doğan Avcioğlu's The National Democratic Revolution thesis.

[6] Ibrahim Turk, p127.

[7] Ibrahim Turk, p127.

[8] Ibrahim Turk, p143.

[9] http://www.tayyareci.com/digerucaklar/turkiye/1951ve2006/f100.asp

[10] Ibrahim Turk, p144.

[11] Ibrahim Turk, p144.

[12] Ibrahim Turk, p144.

[13] http://www.tayyareci.com/arsiv/gunerkurtulus.asp

[14] Ibrahim Turk, p145.

[15] Ibrahim Turk, p145.

[16] Ibrahim Turk, p145.

[17] Ibrahim Turk, p146.

[18] Ibrahim Turk, p146.

[19] Ibrahim Turk, p147.

[20] Note that 30 August is the Victory Day in Turkey and the Turkish Armed Forces holds a pageant in the capital city Ankara and large ceremonies in all the major cities.

[21] Ibrahim Turk, p143.

[22] http://www.airkule.com/default.asp?page=haber&id=10737

[23] http://www.tayyareci.com/digerucaklar/turkiye/1951ve2006/f100.asp

[24] http://cgibin.rcn.com/jeremy.k/cgi-bin/gzUsafSearch.pl?target=218&content=F-100D

[25] RF-100A was used by USAF and ROCAF only. F-100 Super Sabre in Action, Larru Davis and David Menard, Squadron/Signal Publications, 2003, p11.

[26] North American F-100 Super Sabre, Peter E. Davies and David W. Menard, Crowood, 2003, p148.

[27] Levent Başara, 2011, p50.

[28] Levent Başara, 2011, p10.

[29] Levent Başara, 2011, p5.

[30] Levent Başara, 2011, p10.

[31] Levent Başara, 2011, p11.

[32] http://www.ucuyorum.com/showthread.php?103366-111-Filo-01-06-1962-F100D(54-2743)-%C3%9Ct%C4%9Fm-O-Cemil-Ok%C3%A7u-(%C5%9EEH%C4%B0D)

http://www.tayyareci.com/hvsehitleri/cilt2-1948-65/1961-1965/275.htm

Levent Başara, 2011, p27.

[33] Levent Başara, 2011, p20.

[34] Kıbrıs Şehidi Hv. Plt. Yzb. Cengiz Topel ve 1964 Kıbrıs Hava Harekatı, Hv Svn. Bnb Emin Kurt, Ankara, 2009, p113.

[35] http://www.sabah.com.tr/Yasam/2012/09/10/iste-1983te-dusurulen-turk-jetinin-oykusu

Levent Başara, 2011, 49.

[36] Levent Başara, 2011, p11.

[37] Levent Başara, 2011, p16.

[38] Levent Başara, 2011, p41.

[39] F-100 Super Sabre in Action, Larru Davis and David Menard, Saudaron/Signal Publications, 2003, p30, p32.

[40] http://www.tayyareci.com/digerucaklar/turkiye/1951ve2006/f86e.asp

[41] http://www.tayyareci.com/arsiv/irfansarp.asp

[42] http://www.tayyareci.com/digerucaklar/turkiye/1951ve2006/f86e.asp

[43] http://www.millionmonkeytheater.com/RF-84F.html

[44] http://www.tayyareci.com/digerucaklar/turkiye/1951ve2006/rf84.asp

[45] http://www.tayyareci.com/digerucaklar/turkiye/1951ve2006/rf84.asp

[46] http://www.tayyareci.com/digerucaklar/turkiye/1951ve2006/rf84.asp

[47] http://www.millionmonkeytheater.com/T-33.html

[48] http://www.tayyareci.com/digerucaklar/turkiye/1951ve2006/rt-t33.asp

Türk Hava Kuvvetleri’nin kullandığı jet uçakları, Bölüm 1: 1. ve 2. nesil uçaklar, Doç. Dr. Serkan Özgen, ODTÜ, 2005
[49] http://www.tayyareci.com/arsiv/gunerkurtulus.asp

[50] http://www.tayyareci.com/digerucaklar/turkiye/1951ve2006/rt-t33.asp

[51] http://www.tayyareci.com/digerucaklar/turkiye/1951ve2006/rt-t33.asp

[52] http://www.flightglobal.com/news/articles/11-killed-in-south-african-air-force-c-47-dakota-crash-379897/

[53] http://www.tayyareci.com/digerucaklar/turkiye/1923ve50/c47.asp

[54] http://www.tayyareci.com/digerucaklar/turkiye/1923ve50/at11.asp

[55] http://cgibin.rcn.com/jeremy.k/cgi-bin/gzUsafSearch.pl?target=56-4271&content=UH-19

http://www.helis.com/database/modelorg/1815/

[56] http://www.hvkk.tsk.tr/TR/IcerikDetay.aspx?ID=124

[57] http://www.crwflags.com/fotw/flags/tr%5Eairf.html

[58] Türk Havaciginin Tek Deltasi Convair F-102 Delta Dagger, C4Defence, Sayi 2, p184

Forgotten jets: Convair F-102A/TF-102A Delta Dagger

[59] The year is usually wrongly stated as 1963.

[60] http://www.oguztopoglu.com/2012/04/nilufer-aydan-halit-refig-ses-dergisi.html

[61] http://www.cuneytarkin.com.tr/halitrefig.aspx

[62] Then, it was named 1st Base, Levent Başara, 2011, p4.

How to Set the "tintColor" of the Back Button for Popovers in iOS5

2012-01-19T09:46:00.000+02:00

I am developing an iPad application. After customizing the popover background by setting it red, I tried to set the "tintColor" of the "Back" button on the popover navigation bar. Otherwise, it looks ugly!

As I am developing the application in iOS5, the new appearance protocol makes customization very easy:

- (void)customizeAppearance
{
// set the back button tint color
[[UIBarButtonItem appearance] setTintColor: [UIColor redColor]];
}
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions

{

DBG_CALLED

[self customizeAppearance];

return YES;

}

Note that DBG_CALLED is my debug macro. However, in this case the update is global and the buttons on the toolbar are updated also which is not what I want!

The solution is specifying where to update the bar button items:

- (void)customizeAppearance

{

    // set the back button tint color for the popovers

    [[UIBarButtonItem appearanceWhenContainedIn:[UIPopoverController class], nil] 

                                   setTintColor:[UIColor redColor]];

}

The end result is what I want exactly:

I love the iOS5!

Beware of Greeks Bearing Bonds

2010-12-24T10:37:00.017+02:00

Today I read the "The Sidney Awards" article of The New York Times columnist David Brooks. In the article the author mentions some noteworthy essays of 2010:

"I try not to fall into a rut, but every December I give out Sidney Awards for the best magazine essays of the year, and every year it seems I give one to Michael Lewis...
This year it was a Vanity Fair piece called “Beware of Greeks Bearing Bonds.”...
His specific subject is Greece, a country that plundered its public institutions while spoiling and atomizing itself...
Lewis’s genius was to show how the moral breakdown spread into one of the most remote institutions on earth, a 1,000-year-old monastery cut off by water, culture and theology that, nonetheless, managed to put itself at the center of the great plundering."

I decided to read the essay published on October 1, 2010. It is definitely a very interesting one and I strongly recommend reading it to everybody! Apparently, the economic collapse of Greece was accompanied or preceded by moral collapse. The summary of this very nice essay is below:

Beware of Greeks Bearing Bonds*

After systematically looting their own treasury, in a breathtaking binge of tax evasion, bribery, and creative accounting spurred on by Goldman Sachs, Greeks are sure of one thing: they can’t trust their fellow Greeks.

In addition to its roughly $400 billion (and growing) of outstanding government debt, the Greek number crunchers had just figured out that their government owed another $800 billion or more in pensions. Add it all up and you got about $1.2 trillion, or more than a quarter-million dollars for every working Greek.

In just the past decade the wage bill of the Greek public sector has doubled, in real terms—and that number doesn’t take into account the bribes collected by public officials. The average government job pays almost three times the average private-sector job...The retirement age for Greek jobs classified as “arduous” is as early as 55 for men and 50 for women...In Greece the banks didn’t sink the country. The country sank the banks.

The scale of Greek tax cheating was at least as incredible as its scope: an estimated two-thirds of Greek doctors reported incomes under 12,000 euros a year—which meant, because incomes below that amount weren’t taxable, that even plastic surgeons making millions a year paid no tax at all. One reason no one is ever prosecuted...is that the Greek courts take up to 15 years to resolve tax cases. The Greek state was not just corrupt but also corrupting...the credit boom had pushed the country over the edge, into total moral collapse.

In 2001, Greece entered the European Monetary Union, swapped the drachma for the euro, and acquired for its debt an implicit European (read German) guarantee. Greeks could now borrow long-term funds at roughly the same rate as Germans—not 18 percent but 5 percent. To remain in the euro zone, they were meant, in theory, to maintain budget deficits below 3 percent of G.D.P.; in practice, all they had to do was cook the books to show that they were hitting the targets...Any future stream of income that could be identified was sold for cash up front, and spent.

...In late 2008, news broke that Vatopaidi [Monastery] [1] had somehow acquired a fairly worthless lake and swapped it for far more valuable government-owned land. How the monks did this was unclear—paid some enormous bribe to some government official, it was assumed. No bribe could be found, however. It didn’t matter: the furor that followed drove Greek politics for the next year. The Vatopaidi scandal registered in Greek public opinion like nothing in memory...“Without Vatopaidi, Karamanlis is still the prime minister, and everything is still going on as it was before.”

After the new party (the supposedly socialist Pasok) replaced the old party (the supposedly conservative New Democracy), it found so much less money in the government’s coffers than it had expected that it decided there was no choice but to come clean.The prime minister announced that Greece’s budget deficits had been badly understated—and that it was going to take some time to nail down the numbers.... In came the I.M.F. to examine the Greek books more closely; out went whatever tiny shred of credibility the Greeks had left. “How in the hell is it possible for a member of the euro area to say the deficit was 3 percent of G.D.P. when it was really 15 percent?” a senior I.M.F. official asks. “How could you possibly do something like that?”

Among the first moves made by the new minister of finance [George Papaconstantinou] was to file a lawsuit against the Vatopaidi monastery, demanding the return of government property and damages. Among the first acts of the new Parliament was to open a second investigation of the Vatopaidi affair, to finally nail down exactly how the monks got their sweet deal.

In a society that has endured something like total moral collapse, its monks had somehow become the single universally acceptable target of moral outrage. Every right-thinking Greek citizen is still furious with them and those who helped them, and yet no one knows exactly what they did, or why.

In the late 1980s, Vatopaidi was a complete ruin—a rubble of stones overrun with rats. The frescoes were black. The icons went uncared for. The place had a dozen monks roaming around its ancient stones, but they were autonomous and disorganized.

That changed in the early 1990s, when a group of energetic young Greek Cypriot monks...saw a rebuilding opportunity: a fantastic natural asset that had been terribly mismanaged. [Father] Ephraim set about raising the money to restore Vatopaidi to its former glory. He dunned the European Union for cultural funds. He mingled with rich Greek businessmen in need of forgiveness. He cultivated friendships with important Greek politicians. In all of this he exhibited incredible chutzpah. For instance, after a famous Spanish singer visited and took an interest in Vatopaidi, he parlayed the interest into an audience with government officials from Spain. They were told a horrible injustice had occurred: in the 14th century a band of Catalan mercenaries, upset with the Byzantine emperor, had sacked Vatopaidi and caused much damage. The monastery received $240,000 from the government officials

...Most famously, until scandal hit, Prince Charles had visited three summers in a row, and stayed for a week each visit.

From an ancient deed to a worthless lake the two monks had spun what the Greek newspapers were claiming, depending on the newspaper, to be a fortune of anywhere from tens of millions to many billions of dollars. But the truth was that no one knew the full extent of the monks’ financial holdings...And the business had started with nothing to sell but forgiveness.

The day before I left Greece the Greek Parliament debated and voted on a bill to raise the retirement age, reduce government pensions, and otherwise reduce the spoils of public-sector life...Thousands upon thousands of government employees take to the streets to protest the bill...Two months earlier, on May 5, during the first of these protest marches, the mob offered a glimpse of what it was capable of. Seeing people working at a branch of the Marfin Bank, young men hurled Molotov cocktails inside and tossed gasoline on top of the flames, barring the exit. Most of the Marfin Bank’s employees escaped from the roof, but the fire killed three workers, including a young woman four months pregnant...The events took place in full view of the Greek police, and yet the police made no arrests.

The question everyone wants an answer to is: Will Greece default?...It behaves as a collection of atomized particles, each of which has grown accustomed to pursuing its own interest at the expense of the common good. There’s no question that the government is resolved to at least try to re-create Greek civic life. The only question is: Can such a thing, once lost, ever be re-created?

* http://www.vanityfair.com/business/features/2010/10/greeks-bearing-bonds-201010
[1] The Wikipedia article:Vatopedi Monastery.

Failed Romanian Attempt to Manufacture Airliners: ROMBAC 1-11

2010-11-28T01:24:00.022+02:00

ROMBAC 1-11 [WikiMedia image by Luc Willems]

Romania when led by Nicolae Ceauşescu attempted to manufacture British BAC 1-11 airliners in the late 1970s: it was hoped to manufacture up to 80 aircraft for the so called "third world countries" including the Rolls-Royce Spey engines. The aircraft was redesignated ROMBAC 1-11.

Interestingly, the Romanians invested heavily to manufacture western aircraft engines. The Romanian manufacturer Turbomecanica S.A. web site says:

"The best available manufacturing equipment was purchased, and licenses to manufacture and build Viper 633-41, Turmo IV C engines and PUMA helicopter gearboxes and rotorheads were obtained from Rolls-Royce, Turbomeca and Aerospatiale respectively. Due to the lack of reliable local sources for special components, accessories, and tooling, the facility was required to produce all this material on a self-sufficient basis, but at the expense of efficiency. The size of the company was gradually increased, to accommodate an estimated capacity of 4,400 employees....In 1980, a license was obtained ... from Rolls-Royce for the manufacture of the Spey 512-14 DW civil turbofan, powering the Romanian built variant of the BAC-111-500 airliner." [1]

When the Romanians selected the BAC 1-11 to licence built [2], it was a failure already: Boeing 737, McDonnell Douglas DC-9 and Fokker F-28 had dominated the market. The airliner proved to be noisy, underpowered and uneconomical.

"Between 1972-1982 only 35 1-11 were built...This [The last delivery] took place on 30 May 1984. A total of 235 aircraft had been delivered from Hurn and Weybridge." [3]

"There were two reasons why the production line was kept open [1972 onwards]...: first, BAC hoped that Rolls-Royce would develop a quieter and more powerful version of the Spey engine, making possible further One-Eleven developments; second, throughout the early part of the period Romania was negotiating to buy the entire One-Eleven programme and transfer production of the type to Bucharest." [4]

As the Rolls-Royce was recovering from the bankruptcy, it did not design quieter and more powerful versions of the Spey engine. However, the Romanians insisted to manufacture the BAC 1-11!

"The first flight of a Rombac 1-11 YR-BRA took place on 18 September 1982. Production continued until the 9th and last ever new production 1-11 YR-BRI came off the line. It's first flight took place in April 1989. It was delivered to Romavia in 1991...2 further airframes remained incomplete in Romania." [5]

At the end, the Romanians procured airframe and engine licenses of a failed design and manufactured just 9 airliners without any export success! What a huge financial loss! George Friedman of STRATFOR wrote recently:

"Ceausescu decided to pay off the national debt. His reason seemed to flow from his foreign policy — he didn’t want Romania to be trapped by any country because of its debt — and he repaid it by selling to other countries nearly everything that was produced in Romania. This left Romania in staggering poverty; electricity and heat were occasional things, and even food was scarce in a country that had a lot of it. The Securitate, a domestic secret police whose efficiency and brutality were impressive, suppressed unrest. Nothing in Romania worked as well as the Securitate." [6]

In Europe Stage III noise abatement regulations took effect in March 2003 and effectively grounded the infamously noisy BAC 1-11 there, although it continues to fly like in very small numbers in other parts of the world:

"...as of November 2010 there are less than 10 aircraft still in service and many of these only fly occasionally." [7]

Finally, on 12 February 2010, the European Aviation Safety Agency revoked the Type Certificate for the BAC 1-11. [8]

I think the ROMBAC 1-11 disaster is a brilliant example of "irrational" industrialization attempt: nationalism and wishful thinking blind eyes. Simply procuring licenses by pouring money at the expense of lower life standards for the citizens is no substitute for decades long research and development work in many areas! The developed countries know very well the developing countries look for shortcuts and exploit it skillfully.

Final note: it looks like that as of 2009 all the ROMBAC 1-11's are retired.

[1] http://www.turbomecanica.ro/history/the-age-of-jet-engines/

[2] According to the Wikipedia article, the contract signed on 9 June 1979.

[3] http://www.bac1-11jet.co.uk/bac1-11jet.co.uk%20History.htm

[4] Wikipedia article.

[5] http://www.bac1-11jet.co.uk/bac1-11jet.co.uk%20History.htm

[6] http://www.stratfor.com/weekly/20101115_geopolitical_journey_part_3_romania?utm_source=GJourney&utm_medium=email&utm_campaign=101116&utm_content=readmore&elq=d1f11346bb8846b6b2a94972d409a8f8
[7] http://www.bac1-11jet.co.uk/bac1-11jet.co.uk%20History.htm

[8] http://www.easa.europa.eu/ws_prod/c/doc/Design_Appro/EASA%20Certification%20Information%202010-1.pdf

Osmanlı Donanmasında Buhar ve Zırh Devrimi 1830-1876

2010-11-14T00:07:00.345+02:00

Toplumsal Tarih dergisinin Haziran 2010 sayısının dosya konusu "Modernleşme Sürecinde Osmanlı Askeri Tarihi". Bence makalelerden Emir Yener'a ait "Osmanlı Donanmasında Buhar ve Zırh Devrimi 1830-1876"* ilginç bir yazı. Makale yazarın yüksek lisans tezi esas alınarak kurgulanmış: Iron Ships and Iron Men: Naval Modernization in the Ottoman Empire, Russia, China and Japan from a Comparative Perspective, 1830-1905 (Yüksek Lisans Tezi, Boğaziçi Üniversitesi, 2009). Yazarın konuyla ilgili bir kitabı var: From the Sail to the Steam: Naval Modernization in the Ottoman, Russian, Chinese and Japanese Empires 1830-1905 (Saarbücken, Lambert Academic Publishing, 2010).

"19. yüzyıl dünya tarihinde deniz gücünün altın çağıydı...Makineleşen savaş filolarının katlanarak artan stratejik hareketliliği ve ateş gücü sayesinde Batı devletleri [sic] 1815 yılında dünya topraklarının %35'i oranındaki hakimiyet oranını 1914 yılında %85'e çıkartabilmişlerdi...19. yüzyıl dünyasında Osmanlı İmparatorluğu da taşıdığı büyük güç sıfatını koruyabilmek için kendi deniz kuvvetlerini sürekli yenilemek üzere çaba göstermiştir. Bu çaba Sultan Abdülaziz'in saltanatı sırasında dünyanın dördüncü büyük zırhlı filosunun kurulması ile doruğa ulaştı. Ne var ki...93 Harbi'ni izleyen 20 yıl içerisinde bu devasa filo adeta eriyip yok oldu." [1]

1853'de Sinop Savaşı'nda Ruslar Osmanlı Donanması'nı yok ettiler: Amiral Pavel Nakhimov filosunu büyük bir maharetle yönetti. Bu savaş yelkenli gemilerle yapılan son büyük deniz savaş sayılsa da her iki tarafta buharlı küçük savaş gemileri vardı. Kırım Savaşı'nda Fransız Lave sınıfı floating battery'ler başarılı olunca, özellikle Kinburn Savaşı'nda, bütün büyük donanmalar yelkenli savaş gemilerinin zırhlı buhar makineli savaş gemileriyle yenilemeye başladılar.

"Buharlı gemi emperyalizmin en önemli silahlarından birisi olarak böylece [buharlı gemiler sayesinde Batı donanmalarının küresel erişim kazanmaları] ortaya çıktı. İlk buharlı gemiler her ne kadar asker sevkiyatında ve geleneksel muharebe birimleri olan yelkenli kalyonları yedekleme işlerinde vazgeçilmez olsalar da, yeterli miktarda silah taşımalarını engelleyen çarkları yüzünden en fazla filo destek üniteleri olarak kalmaya mahkum olmuşlardı. Bu durum 1840'larda uskurun icadi ile değişti." [2]

İlk uskurlu kalyon Fransız donanmasına 1850 yılında katılan Napoléan oldu. Ünlü Fransız deniz araçları tasarımcısı Henri Dupuy de Lôme tarafından tasarlanan bu savaş gemisinin yelkenleri de vardı ve ahşaptı. Kırım Savaşı'nda tüm dikkatleri üzerine çekmişti.

"Buhar makinesinin savaş filosunu dönüştürmesinin ardından gelen ikinci adım, gemilere metal zırh kaplanması idi...Ancak yangın mermilerinin yaygın kullanıldığı Doğu Asya'nın aksine, Avrupa sularında genel norm som demir gülleler kullanmak olduğundan gemi zırhlanmasına ihtiyaç duyulmamıştı. Bu durum 1822 [3] yılında Fransız ordusundan Albay Paixhans'ın yangın mermisi atan ağır bir top üretmesi ile değişti."

"1859 yılında tamamlanan [Fransız] Gloire, tarihin ilk açık deniz zırhlı muharebe gemisi idi ve 36 top taşımaktaydı. Gövdesi ahşap üstüne demir kaplama idi."

"...İngiliz donanmasından bir Kırım Savaşı gazisi olan Albay Cowper Coles ise çapları ve boyları giderek büyüyen topların makul boyutlarda bir gövdeye nasıl yerleştirilecekleri sorununa 1862 ylında döner top kulesi ile etkili bir çözüm geliştirdi. Top kulesi ayrıca yelkenin de kesin sonunu getirmiştir...1873 yılında genç İtalyan donanması için kızağa konulan Duilio ve Dandolo [4] zırhlıları iki adet top kulesinde toplam dört adet 17 pusluk top taşıyor, çelikle güçlendirilmiş bir zırh kuşağı ile korunuyor ve hiçbir yelken taşımıyorlardı. Onların inşası ile beraber modern zırhlı savaş gemileri çağı kesin olarak başladı. Artık deniz gücü olmak zırhlı sahibi olmak ile belirlenecekti." [5]

1830 Londra Antlaşması ile Yunanistan bağımsızlığını kazanıp barış geldiğinde Osmanlı donanması tükenmiş durumdaydı:

* Napolyon'un 1798 Mısır seferinden beri süregelen aralıksız savaşlar,

* Navarin Savaşı'nda (1827) uğranılan çok ağır kayıplar,

* Yunan ayaklanması nedeniyle çok önemli olan Rum leventlerin atılması.

"Barışın tesis edilmesiyle beraber Sultan II. Mahmud donanmayı tekrar ayağa kaldırmak için harekete geçti. Bu yenileme programının üç temel amacı kaybedilen gemilerin yerine en son teknolojik sistemde yeni birimler koymak, mürettebat kıtlığı sorununa çözüm getirmek ve kifayetlerini yükseltmek ve en önemlisi, donanmanın idaresini merkezileştirip subayları profesyonelleştirmek olarak özetlenebilir.

Osmanlı İmparatorluğu'nun hem gemi yapımı için elverişli malzemeler açısından zenginliği hem de ... Tersane-i Amire'nin kifayeti özellikle yabancılar tarafından sık sık dile getirilmiştir." [6].

Mahmudiye, Haliç'teki Tersâne-i Âmire tarafından 1829'da yapıldı ve 1875'e kadar kullanıldı. Uzunca bir süre süre için dünyadaki en büyük savaş gemisiydi.

Görünüşe göre Osmanlılar'ın iyi amiralleri ve denizcileri pek yoktu, ama yelkenli savaş gemisi yapmasını iyi biliyorlardı:

"Mahmudiye (1829), ordered by the Ottoman Sultan Mahmud II and built by the Imperial Naval Arsenal on the Golden Horn in Istanbul, was for many years the largest warship in the world." [7]

Bozuk ilişkiler nedeniyle İngiltere ve Fransa'dan teknoloji alamayan Osmanlı İmparatorluğu Amerika Birleşik Devletleri'ne yöneldi:

"Yetenekli gemi yapımcısı Foster Rhodes Kaptanıderya [sic] Çengeloğlu Tahir Paşa'nın koruması altında birçok gemi inşaat etmiş, ayrıca buhar gücünün Osmanlı donanmasına girişine büyük katkıda bulunmuştur...Yerel inşaatlar Foster Rhodes'in buharlı gemi inşaatı için düzenlediği Aynalıkavak Tersanesi'nde gerçekleştirilmişlerdi.

Osmanlı donanmasında ilk buharlı filotila 1848 yılında inşa edilen dört adet Taif sınıfı [8] yandan çarklı fırkateyn ile kuruldu...1851 yılında Mısır Hıdivi [sic] Abbas Paşa tarafından Sultan Abdülmecid'e hediye edilen 22 toplu Muhbir-i Sürûr fırkateyni ise Osmanlı donanmasının ilk uskurlu savaş gemisi oldu.

Donanma için insan gücü kıtlığını çözmek ise gemi inşaatı kadar kolay olmadı...mürettebat kıtlığı sorunu hiçbir zaman tam anlamıyla çözülememiştir.

1845 yılında donanma ıslahatını yürütmek içim kurulan Meclis-i Bahrî'nin çalışmaları 12 Mart 1867 tarihinde Tersâne-i Âmire ve Donanma-i Hümayûn iaderelerinin birleştirilmesi, Kaptanıderyalık [sic] makamının ilgası ve Bahriye Nezareti'nin kurulması ile sonuçlandı." [9]

Görünüşe göre Mekteb-i Bahriye 1851'de Heybeliada'da açılıyor. Ayrıca:

"...Meclis-i Bahrî''nin 1853 tarihli rütbe reformu ile deniz subaylarının rütbeleri açık ve net bir hiyerarşi ile yeniden düzenlenmiştir." [10]

Mesudiye, Aralık 1875'de hizmete girdi ve 13 Aralık 1914'de İngiliz B11 denizaltısı tarafından Çanakkale'de batırıldı.

Osmanlılar, Kırım savaşı sonrası çağa ayak uydurmak için çok sayıda savaş gemisi yaptırdılar. Örneğin İngiltere'den satın alınan ve 1875 yılında teslim alınan Mesudiye "ironclad" için:

"..hizmete girdiği sırada dünyanın en büyük savaş gemisiydi..." [11]

deniyor. Bu iddia doğru olmayabilir, ama muhtemelen aynı zamanda sipariş edilen ama teslim edilmeyip İngiliz donanmasına katılan savaş gemileri için ArGe masraflarını Osmanlı hükümeti yüklendi!

"İki yüzden fazla İngiliz ustabaşı ile kalifiye işçi gerekli teknik deteğin sağlanması için istihdam edilmekteydi. Tersâne-i Âmire imparatorluğun en büyük sanayi kuruluşu haline geldi.

Ne var ki, Osmanlı İmpaeratorluğu'nu birinci sınıf bir deniz gücü haline getiren bu olağanüstü atılım ekonomik olarak çok ağır sonuçlara yol açtı....Silahlanma programı ancak kontrolsüzce alınan dış kredi ile yürütülebiliyordu ki bu borçlanma, 1873 küresel finans krizi ardından 1876 Osmanlı moratoryumuna yol açacaktı." [12]

"1876 yılında Aziziye zırhlısına atanan Mülazım Süleyman Nutkî, savaş filosunun bu en güçlü üyelerinden birinde düzen ve disiplin yerine noksan mürettebat, baştan savma talim ve alaylı-mektepli olarak ikiye bölünmüş, birbirinden nefret eden bir subay kadrosu bulunca şaşırmştı. Ne yazık ki bu resim dış kredi ile kurulmuş etkileyici zırhlı filosunun ardında yatan esas görüntüyü yansıtmaktaydı...Rusya Karadeniz'de savaş filosu kurmaktan men edildiği için '93 harbi (1877-78) esnasında Osmanlı donanmasın karşısında bir avuç mayın gemisi ve silahlandırılmış ticaret gemisi haricinde bir güç bulunmuyordu. Bu duruma rağmen sonuç tam bir fiyasko oldu...Halbuki Osmanlı donanması mevcut gücünün yarısıyla bile hamlede bulunsa yapacağı bir çıkartma ile Balkanlar'da ilerleyen Rus ordusunun ikmal hattını kesip büyük bir zafere imza atabilirdi.

Maliyeyi iflasa sürükleyen donanma programından alınan bu olumsuz sonuç hem yönetici kesimde hem kamuoyunda büyük infiale yol açtı. "Donanma istemezük!" solganı duyulan yaygın tepkiyi ifade etmekteydi. Sultan II. Abüdlhamid saltanatında Osmanlı imparatorluğu deniz gücü olmak iddiasını kesin olarak kenara koydu. Artık öncelik savaş filosuna değil istihkâmlar, mayınlar ve torpil gemilerine dayalı sahil müdafaa stratejisine verilecekti." [13]

"Ancak kıyı savunmasında da aşırıya kaçılarak çekirdek bir savaş filosunun olsun korunamaması neticesinde, Ege Denizi'nin savunması aşındı ve Balkan Savaşları'nda Yunanistan'ın Ege adalarını ele geçrimesine engel olunamadı." [14]

Bence Osmanlılar'ın yarım yüzyıla yakın bir süre donanmaya çok büyük kaynak ayırıp çok az sonuç almaları "akılsızca" silahlanmaya çok güzel bir örnek. Doğru dürüst yüksek okullar açmadan, hiçbir ArGe merkezi kurmadan "şark kurnazlığı" ile kestirme yollardan ilerlemeye çalışmak çok büyük bir hata. Savaş gemileri güçlü bir donanmanın görünen yüzü, ama bunları etkin kullanabilecek yöneticiler ve subaylar olmadan ve sürekli dış borçla mühendislik satın alarak ne elde edilebilir? Osmanlı hükümetleri donanmaya bu kadar kaynak ayırırken tam olarak ne öngörmüşlerdi? Bu kadar uzun bir süre bu kadar ölü bir yatırım yapmakta ısrar edilmesine şaşırmamak elde değil. Muhtemelen Osmanlı İmparatorluğu'nun kuruyup çökmesinde bu "akılsızlığın" ciddi bir etkisi var.

* Emir Yener, "Osmanlı Donanmasında Buhar ve Zırh Devrimi 1830-1876", Toplumsal Tarih, Tarih Vakfı, Haziran 2010, s.54-60

[1] s.54

[2] s.55

[3] Wikipedia'daki Paixhans Gun maddesinde 1822-3 yılları ve General rütbesi belirtiliyor.
[4] Wikipedia'da bu savaş gemileri Caio Duilio ve Enrico Dandolo olarak görünüyor.

[5] s.56

[6] s.57

[7] Wikipedia'da Mahmudiye maddesi.

[8] Türkçe Wikipedia'da Mecidiye Sınıfı diyor: Dağılma dönemi Osmanlı donanması.

[9] s.57

[10] s.58

[11] s.59. Wikipedia'da Ottoman battleship Mesudiye maddesinde "she was the largest casemate warship ever constructed...at the time was considered one of the most powerful warships in the world." deniyor.

[12] s.59

[13] s.60

[14] s.60

Image retrieval with PHP

2010-11-05T09:05:00.000+02:00

I developed a Flickr.com related project for an STB. The clients display the "Interesting Photos", allow search and full screen viewing, etc. The server-side coding is done with the PHP. Due to security issues the STB doesn't allow direct access to the outside world. As I didn't want to first download and then serve the images, I needed a method to serve the JPEG images directly. I found the small img.php file listed below works flawlessly:

The key point is not inserting anything outside the PHP block: let the file starts with the "<?php" and ends with the "?>".

Then, the STB clients simply prefix the requested image URL's with "img.php?url=" like this:

img.php?url=http://farm4.static.flickr.com/3587/3617423550_c6c6923569.jpg

Enjoy...

Çanakkale Üzerinde Bir Şahin: Hans Joachim Buddecke (1890-1918)

2010-10-31T20:20:00.001+02:00

Hans Joachim Buddecke* (22 Ağustos 1890 – 10 Mart 1918) erken dönem Alman aslarından bir Birinci Dünya Savaşı uçucusu, "Chef der Flieger auf Galipoli"**. Buddecke, Mayıs 1916'da Prusya Krallığı'nın en önemli askeri madalyası olan Pour le Mérite ile ödüllendirildi: Max Immelmann ve Oswald Boelcke'den sonra bu madalyayı alan üçüncü pilot. Buddecke, Lens, Fransa üzerinde Naval 3, RNAS'a ait Sopwith Camel avcı uçaklarıyla yapılan bir hava savaşında öldü. Asker olan babası, ölümünden sonra 1918'de anılarını "El Schahin" adıyla yayınladı. Önsözde "Bu anılar, İzmir'de bulunduğu sırada yazıldı" diyor. Bu kitabı Türkiye İş Bankası Kültür Yayınları Bülent Erdemoğlu çevirisiyle yayınladı***. Zaten ben de ondan bu kitap sayesinde haberdar oldum.

Çevirmen, "Askeri havacılığımızın kuruluşunda emeği geçenleri, Kıbrıs'ta Amerikan ambargosu sonucu alçaktan uçmak zorunda kalarak şehit düşürülen Pilot Yüzbaşı Cengiz Topel başta olmak üzere görev başındaki tüm havacılarımız ile görevi sırasında can vermiş havacılarımızı burada saygıyla anmak istiyorum." [1] diyor. Eskişehir konuşlu 112. Filo'nun bir uçucusu olan Hv. Plt. Yzb. Cengiz Topel, 8 Ağustos 1964'de Yunan hücumbotlarına alçak irtifadan F-100D Super Sabre uçağıyla saldırırken uçaksavar ateşiyle düşürüldü. Uçağının kendi attığı bombalardan isabet alarak düştüğü de söyleniyor [2]. "Amerikan ambargosu sonucu alçaktan uçmak zorunda kalarak sehit düsürülmesi" açıklamasının pek doğru olduğunu sanmıyorum: çok hızlı yön değiştiren gemilere güdümsüz bombalarla alçak irtifadan saldırmak garip değil. Zaten Amerikan ambargosu Şubat 1975-Eylül 1978 arasında gerçekleşti.

Kitabın başında Türk askeri havacılığının doğuşunun güzel bir özeti var. Çevirmen, 2008'de Çanakkale'de tesadüfen tanıştığı emekli eczacı Şevki Suda'dan öğrendiklerini yazıyor:
"... babam hep anlatırdı, savaşta Bodege diye bir Alman pilotunu bire bir tanımış." Bunun üzerine 1940 doğumlu Şevki Suda'dan 1888 doğumlu Hüseyin Kazım Suda'dan dinlediklerini anlatmasını rica ettim. Girit'in Hanya kentinde doğan Yargıtay'dan emekli Hüseyin Kazım Suda, Hukuk Fakültesi'nde öğrenciyken 1915'teki Seferberlik'te okulu bitirmeden İstanbul'da askere alınıyor. Rumca bildiğinden, sivil giysili istihbaratçı olarak askerlik görevini yapmaya başlıyor. Çanakkale savaştan dolayı boşaltılınca, Suda ve ailesi Çanakkale'nin kuzeyindeki Özbek Köyü'ne göçüyor. Hüseyin Kazım Bey savaş sırasında herhalde bu taşınma işine yardım için olsa gerek, kısa süreli bir izinle ailesinin yanına geliyor. Bu sırada "Mülazım Bodege"nin hava çarpışmalarının tanığı oluyor....Bodege Çanakkale'de çok bilinen bir adam. Ölüm haberi gelmiş kente. Millet bayağı bir matem yapmış. Kim olduğunu biliyorlar. Çünkü Bodege burada halkın arasında yaşarmış." [3]

Anılar, yazarın Hassa Alayı'nda Teğmen iken "görmek" için İndianapolis'e gitmesiyle başlıyor. Burada ilk uçağını satın alıp kendi kendisine pilotluğu öğreniyor. Buddecke tam da uçak üretimi için bir grup işadamıyla anlaşmak üzereyken Birinci Dünya Savaşı çıkıyor. Vatansever Alman genci kimliğini gizleyerek ülkesine dönüyor ve askeri pilot oluyor: "Indianapolis'te yaşayan tüm Alman aileler, geniş bir salonda toplanarak, Kayzer ve vatan için üç kez "Hurra!" diye bağırdılar. Birbirimize danışarak Almanya'ya nasıl gideceğimizi konuştuk. Yaşlı Amerikalı Almanlar bizim için önemli ölçüde yardım sağlamışlardı. New York'a ilk olarak ben gittim...Benim kadar çok çabalayan yoktu." [4]

Buddecke'nin düşürdüğü 13 uçağın listesi kitapta yok, ama Internet'de var. Kitapta genel olarak tarihlerin ve uçtuğu/düşürdüğü uçak modellerinin belirtilmemesi talihsizlik. Görünüşe göre Fokker Eindecker, Fokker E.III [5], Halberstadt D.II ve Pfalz D.IIIa ile uçmuş.

Buddecke, ilk hava savaşlarını ve Braunschweig Dükü ve Prens August Wilhelm'in ziyaretlerini anlatıyor. Sonra, Türkiye'ye gitmek için gönüllü oluyor ve Aralık 1915-Nisan 1916 arası Gelibolu'da uçuyor: ulaşım çok zor ve yaşam koşulları pek zorlu: "Gelibolu'da büyük bir pilot sıkıntısı vardı. Düşman uçak birlikleri, bombalamak istedikleri her yere sorunsuzca gelebiliyorlardı...İyi pilotlarla donanmış üç Fokker [avcı uçağı], artık kendisini gösterebilirdi. Üç pilot, altı teknisyen ve bir çevirmenden oluşan birliğin yönetimi bana verildi. Gerekli diğer kişilerle araç gereci, kendim bölgeden bulacaktım." [6]

Buddecke, bu dönemde 4 kesin ve 7 olası hava zafer kazanıyor. Osmanlı Hava Kuvvetleri'nin başındaki Erich Serno ile görev yapıyor, denizaltıcı Otto Hersing'den [7] övgüyle bahsediyor ve Liman von Sanders ile tanışıyor. Ikinci düşürdüğü ve Gelibolu'daki ilk kesin başarısından sonra inişini anlatıyor: "Buraya doğru koşusan insanların gözünde, acımayla karışık bir gülümseme vardı. Elerimi, elbiselerimi ve ayakkabılarımı öptüler. "Allah herşeye kadirdir" dediler "...ve Almanlar." O akşam kutlamalar yağdı." [8] O gün düşürdüğü ilk uçak sanıyorum denize düştüğü için "olası" kalıyor. "Bunun [İngilizler'in çekilişinin] duyumunu aldık. Böylece, burada büyük bir savaşım kazanılmış oldu. Aynı gün, bir önceki akşam olanları izlemiş olan bir Türk köylüsü, bana bir tencere yoğurdu armağan etti. Yoğurt çok lezzetliydi." [9] Enver Paşa, Buddecke'nin bir hava zaferine tanık oluyor, onunla tanışıyor ve bir madalya takıyor. [10]

Buddecke Batı cephesine dönünce Jasta 4 ile uçuyor ve üç kesin zafer kazanıyor. Pilotlar arasındaki rekabetten bahsediyor: "Başkasının yine bir tanesini düşürdüğünü duymak, herkesin hoşuna gitmiyordu." [11] Eski dostu Jasta 4 komutanı Rudolph Berthold Jasta 14'ün başına getirilince Jasta 4 komutanı Buddecke oluyor: anılarında bunu belirtmemesi ilginç.

Buddecke Aralık 1916'da Türkiye'ye geri dönüyor: "...yeniden Çanakkale. Gezici sirkimin buraya ulaşması, uzun bir yolculuğun sonunda gerçekleşmişti...Burada dövüşmek, Fransa'da olduğundan değişikti. Orada her şey el altındaydı. Yeni bir uçak için bir söz yetiyordu." [12] Görünüşe göre Buddecke Izmir yakınlarındaki bir Alman filosuna atanıyor ve Gelibolu'dan geçerek yeni görev yerine gidiyor: muhtemelen buradaki uçucularla beraber. Birkaç defa yer değiştirdikten sonra İzmir semalarındaki ilk hava savaşında silahları sorun çıkardığı için uçak düşüremiyor. [13] "Bir telgraf , beni ivedilikle İzmir'e çağırıyordu. "Şehrin üzerinde uçaklar var." Sabah erken, Körfez'deki alana iniş yaptım ve gizlendim. Elde olanların tümüyle kuş kamufle edildi. Bu biçimde iki gün pusuda bekledim. Üç gün sonra..."İzmir'e doğru üç uçak" diye bildirdi." [14] Anladığım kadarıyla Buddecke "sirkini" düşman hava faaliyetleri raporlarına göre konuşlandırıyor. "Şimdi savaş hiç istemediğim biçimde kent üzerinde olacaktı. Tüm uluslardan izleyicilerle dolu bir tiyatro sahnesinde gerçekleşecek bir çarpışmanın sonucunu kimse bilemezdi." [15] Arka arkaya iki zafer kazanarak sahneden yüzünün akıyla çekiliyor. [16] "Üzerimde olan ve görmemiş olduğum bir üçüncü, eve dönüş yolunu tuttu." [17] "İzmir kenti, koruyucusuna değerli bir altın plaket vererek teşekkür etti." [18]

Kitabın son bölümü "Anadolu Manzaraları" başlıklı: Buddecke burada Anadolu içlerine yaptığı uzunca süren bir av gezisinden bahsediyor. İsmini belirtmediği küçük bir kasabada önde gelen bir ailenin evinde kalıyorlar. Hamama gidişlerini, sonrası akşam yemeğini ve yer yatağında yatışlarını anlatıyor. İzmir semalarından düşman uçaklarını söküp atan Alman pilotu misafirperlikle ağırlayan bu ailenin tam olarak bulunması çok hoş olur!

1918 başında Türkiye'den ayrıldıktan kısa bir süre sonra ölen bu kahraman Alman pilotu saygıyla anıyorum. Berlin'e yolum düşerse Invalidenfriedhof Mezarlığı'na gidip mezarını ziyaret edeceğim: "Ruhe in Frieden".

* http://en.wikipedia.org/wiki/Hans_Joachim_Buddecke
** Osmanlı havacı üniformasıyla güzel bir fotoğrafı: Sanke Card #371
*** Çanakkale Üzerinde Bir Şahin, Hans Joachim Buddecke, Çeviren ve Hazırlayan: Bülent Erdemoğlu, Türkiye İş Bankası Kültür Yayınları, 1. Baskı, Mart 2009, xxv+123 sayfa

[1] s.vii
[2] http://www.tayyareci.com/hvtarihi/cengiztopel/yerde.asp
[3] s.xxii
[4] s.22
[5] Fokker E.III 345/15, Oblt. Hans Joachim Buddecke: http://www.mincbergr.net/index.php?page=fokker-e-iii-345-15
[6] s.56
[7] s.63. Bkz. Çanakkale Denizaltı Savaşı, Otto Hersing, Çeviren: Bülent Erdemoğlu, Türkiye İş Bankası Kültür Yayınları, 2007
[8] s.76. Muhtemelen 6 Ocak 1916.
[9] s.76
[10] s.81. Muhtemelen 12 Ocak 1916.
[11] s.95
[12] s.105
[13] s.109
[14] s.110
[15] s.111.
[16] s.111. Muhtemelen 30 Mart 1917.
[17] s.111
[18] s.122

"switch...case" vs "if...else if" for String Handling

2010-10-21T14:28:00.000+03:00

I posted to the Devx.com forum a suggestion for handling a string via "switch...case" instead of "if...else if" and asked expert opinion in June 2007:

We use C for developing embedded systems software. A function assigns a function pointer based on the "action_name", see LISTING 1. I don't like such "if...else if" statements although the below one is short and easy-to-follow. Consequently, I replaced the "if...else if" statements to a "switch-case" statement. Certainly, the new code is much longer, see LISTING 2. As I don't use function pointers, but call some static functions there are some other differences. The major issue is deciding what to do. Here, a string holds all the supported actions, namely "s_Actions". The "actions" enum lists the "index" of each "action_name" in this string. For example, "GetCurrentConnectionIDs" "action_name" starts at 17th character. Please note that I separated the action_names with "_".

The advantages of LISTING 2:
1. All the supported actions are clearly listed with the "s_Actions" string.
2. There is only one function call, namely strstr(), to decide what to do instead of N strcmp() calls.
3. The strstr() call works like a hash function as it converts a string to an index. Although, it takes more lines to write, the logic is to closer to how my brain works: I don't think in terms of "if...else if"s because as I know all the supported actions just by looking the "action_name", I decide what to do.

The disadvantages of LISTING 2:
1. It takes more lines and time to develop code.
2. It is necessary to assign "index" numbers manually and updating it may be a boring and error-prone task.

However, I personally prefer LISTING 2 over LISTING 1. What is your opinion? Thanks for your interest.

(All the debug related lines etc are deleted below)

Unfortunately, I haven't received much useful comment. I still believe the technique I suggested is better suited to the embedded systems.

Hayat Mezarda, Stratis Mirivilis (1930)

2010-10-12T15:36:00.006+03:00

Midilli'li Stratis Mirivilis'in (1890-1969) gözden geçirilmiş baskısı 1930'da çıkmış Hayat Mezarda* romanını Dr. Kriton Dinçmen çevirisiyle okudum. Görünüşe göre başka bir çevirisi de var [1]. Yazar, 1912-22 arasını savaşarak geçirmiş görünüyor: Balkan Savaşları, 1. Dünya Savaşı ve ardından Yunanistan'ın Anadolu'yu işgaline katılmış. Eser, yazarın 1. Dünya Savaşı'nda Makedonya Cephesi'nde savaşırken yasadıklarına dayanıyor: Fransa'nın desteklediği Yunanistan Almanya'nın desteklediği Bulgaristan ile azap verici siper savaşları yapmaktadır. Roman, savaşta alev makinesiyle yanarak ölen Çavuş Andonis Kuçulas'ın anılarından oluşuyor ve Yunanistan'da iki defa uzun süre yasaklanmış. Genel olarak "yönetici" sınıf mensupları pek vasat ve sığ olarak resmedilmiş. Özellikle Midilli Ada Tümeni komutanı "Balafaras" lakaplı General göbekli, iri yapılı, gösteriş seven ve askerlerinin yaşamıyla ilgisiz pek vasat birisi olarak neredeyse karikatür gibi duruyor.

Ege hasreti, firar edenler, kurşuna dizilenler, yoğun topçu saldırıları...Roman, I. Dünya Savası’ndaki siper savaşlarıyla ve o dönemle ilgili ayrıntılarla dolu:

s.129: "Alman tayyarecilerin asker grupları üzerine attıkları demirden ok demetleridir."

s.246: [Bir askere karısından gelen mektuptan alıntı] "... paralar tükendi ve simdi ekmekten yoksunuz. Dört gündür kü, Avranitis'in fırınından ekmek alamıyoruz. Ağırına gitmesin...veresiye almaya son gittiğim defa göz kırptı ve bana dedi: önce sen, bir ara yukarıya çık da ödeşelim sonra da gene veresiye sana yaparım. Allah onun belasını versin...Yeğen Stavriça'nın eliyle sana yazan ben karın Asimenia ve sana buse veriyorum."

s.248: [Firar ettiği sanılan mükemmel asker Zafiru'nun cesedi Fransızlardan kalan fosseptik çukurunda bulunur] "... çukuru tepelemesine doldurduk. O zaman da, bir emir çıktı: angaryaya erler çıkacak, eski tahtaları çekip yan tarafa açılacak yeni bir çukurun üstüne koyacak. Aynı angarya ekibi de, eski çukuru taş ve toprakla doldurup tıkayacak. Laf!..taşları uzaktan getirmek gerek...Öyle olunca da, askerler, ...yasak savarcasına çukuru sadece toprakla örtmüşler...Zafiru işemek için helaya gider. O akşam hepimize konyak dağıtmışlardı...Yeni helaya gideceğine , dosdoğru eskisine gider...Dosdoğru dibe!...boklarla tıkanmış olarak can vermiş....Balafaras'ın şöyle yazdığını düşün: 'Zafiriu müttefik Yunan-Fransız bokları ile kahramanca cebelleşerek ölmüştür. Ve, maalesef şerefli ölüm anında ağzı tıkalı olması nedeniyle 'yasasın vatanımız' diye bağıramamıştır...' "

s. 273: "Başka bir gece Fikos, basının yarısı tıraş olmuş gibi uyanmıştı; basta, herkes bunun bir saka olduğunu zannetti; ancak, biraz sonra, Fikos'un yağ kandilinin tam altında uyumuş olması nedeniyle, kandilden damlayan yağın genç çocuğun saçını üstünde kuruduğu, ve farelerin saçın yağlı kısmını yemiş oldukları anlaşıldı."

s.279: [Bulgar siperlerinden gelen] "Türkçe şarkının sözlerini, biz adalılarla Anadolulular iyi kötü anlıyorduk. Ve, bizlerde şarkıyı kalplerimiz de söyledik...İkinci kez o güzelliği tatmamızdan sonra, üstçavuş bir gece devriyesine, Bulgar tellerine vardıklarında, oraya asmak üzere ve kalın Latin harfleri ile "achk olsun, merakli kardach" yazılı bir levhayı verdi...[Şiddetli bir Fransız topçu saldırısından sonra] Şarkıya gelince...bir daha hiç duyulmadı. Karşıdaki şarkı öldürüldü. Kaç defa ön siper tümsekliğine tırmandık...her gece yerlerimizi alıp bekliyorduk...Bir daha...hiç...ama hiç o şarkıyı duymadık."

s.280: "Türkçe bilen pek çok Ayvalıklı ve Edremitli arkadaş yavaş yavaş abrimize sızıp [Firar edip Yunan siperlerine kaçan Bulgar asker] Petrof'un ağzından firar öyküsünü öğrenmeye geliyorlar. O da üşenmiyor ve her yeni gelene yeniden bastan aşağı tüm ayrıntıları ile anlatıyor."

s. 285: "Kendisi [Onbaşı yardımcısı Dimitratos] üç çocuk babası ve evlidir. Birgün karısına söyle bir mektup yollamış. "Sevgili karım. Dört çocuk babası olan askerler siperden kurtulurlar...ne yapıp yap, bir an önce bizim çocukların sayısını tamamla...Sonuç: gönüllü deyyusluk, gönülsüz ölümden evladır...Kasap Apostal'a git ve bu hususta bana yardımcı olması için benim de ricacı olduğumu söyle...Şayet de, -inanmıyorum, ya - bu konuda zorluk çıkaracak olursa, benim de, -simdi ilk kez açıklıyorum- kendi izni olmadan kendisine aynı yardımı yapmış olduğumu söyle. Tereddütleri varsa, Mirgula'ya sorarsa öğrenir..." Sansür, mektubu Alay'a göndermiş."

s.333: "Bölüğün ve bütün alayın içinde tuhaf bir skandal patladı. Dünden beri herkes bundan söz ediyor. Arkadaşım Dimitratos'un siperimizde [para karşılığında] hasta ve sakat üretmekte olduğu anlaşıldı....Soruşturmayı yürüten üsteğmen, hem sırt çantasını hem de yuvasını karıştırmış. "İş"ine ait pek çok ıvır zıvıra rastlamış...Kükürtlü öyle sigaraları vardı ki, hekime ciddi bir hastalığı düşündüren arazlı bir öksürüğe neden oluyordu. Erler kendisine "usta" takma adını vermişler ve hiçbiri kendisini ihbar edemiyormuş."

Ufak tefek Türkçe hataları kitabin tadını biraz bozsa da [2] Egeli bir yazarın 1. Dünya Savası’nı resmedişi kesinlikle okumaya değer.

* Hayat Mezarda! Savaşın Kitabı, Stratis Mirivilis , Çev. Kriton Dinçmen, Arion Yayınevi, 2.Baskı, İstanbul, 2006 [Kitabın adı kapakta "Hayat Mezarda! gençlik siperlerde -savasın kitabı-", iç sayfalarda "Hayat Mezarda!..", "Hayat Mezarda!.. -Savasın Kitabı-" ve Arion Yayınevi web sitesinde "Hayat Mezarda" olarak görünüyor.]
[1] Mezarda Hayat, Stratis Mirivilis , Çev. Nevzat Hatko, Can Yayınları, 1.Baskı, İstanbul, 2008 [Bu başlık romanın İngilizce adı "Life in the Tomb" ile uyumlu gibi duruyor]
[2] Örneğin s.337'de "istdiğimin" sanıyorum "istediğinin" olacak.

Merhaba Turkey: American Military in Turkey

2010-01-05T12:55:00.000+02:00

I accidentally found a web site dedicated to the US military personnel served in Turkey: Merhaba Turkey: "These are the stories of those whose lives changed while serving in the American Military in Turkey". Basically it lists the names of service men, where and when did they serve in Turkey and their memories. I like the site very much! For example, read the following interesting anecdote of SSGT Steve Slezak who served in Diyarbakir in 1970/1:

"I went to work at the radio station for my shift, as usual, which
went into the night hours. Sirens going off, and a call from the Air
Police informed me that the base was under attack from Kurdish
bandits...the guys who looked like they were right out of a grade-B
Arabian movie. They had come down in force, to steal copper out of the
radar emplacements (from what I was told). The copper was sold
downtown."

Plus, Lt. Neil S. Reyer, USAF wrote an article on the "Kordon Hotel" he helped to launch in Izmir in 1966: Izmir's Kordon Hotel - The Beginnings, A2/C Lewis B. Culkin Jr, USAF shared his memories of Trabzon in 1958/9 and A/2C Charles Sibert, USAF submitted a lenghty article on Incirlik Air Base, Adana detailing his service there between March 29, 1958 - January 10, 1960 with a lot of photos. Note that Mr Sibert is looking for Seyit Demirel, Turkish Air Force from Izmir who was sent to Dreux Air Base, France in 1960 for radio training.

I think the photos of this site is very interesting: there are many photographs of Turkey shot between 1950s-70s.

Hanriot 182

2009-12-30T10:38:00.000+02:00

It is widely stated Turkish Air Force operated "Henriot 182"aircraft in the 1940s* for liaison and training tasks:
Henriot 182 @ Official Turkish Air Force Web Site
Henriot 182 @ Tayyareci.com
Henriot 182 @ Ole Nikolajsen
However, when I google'd the web for "Henriot 182" I found only some Turkish sites! After searching the Wikipedia, I found that there is a certain French aircraft manufacturer company named Hanriot which manufactured Hanriot 180 series aircaft. So, I think the aircraft should be referred as "Hanriot 182", not as "Henriot 182".

* Perhaps between 1939-1942.

Yonca Lodge

2009-07-25T13:13:00.000+03:00

Eşimle bir haftalık tatilimizi geçirecek yerleri Internet'de ararken özellikle küçük otellere bakıyordum. 2008'de Antalya'da gittiğimiz 5 yıldızlı büyük otelden hiç memnun kalmamıştık! En kötüsü sabahları sahilde şezlong bulamamaktı. Ayrıca aşırı doluluğun verdiği gürültü çok tatsızdı. Amacımız sessizlik içinde kafamızı dinlemekti ve Google arama sonuçları içinde ordan oraya giderken Yonca Lodge'u* gördüm. Nişanyan'ın Küçük Oteller Sitesi'nde** bir sorun belirtilmeyince 27 Haziran-04 Temmuz, 2009 tarihleri arasında bir hafta kalmak için yer ayırttım. Oteli Karabacak ailesi işletiyor: Şaban Bey ve Hatice Hanım mutfaktalar, oğulları Emre Bey*** idarede. Aile dostları Yeter Hanım da yardım ediyor. Emre Bey ile Dalaman Havalimanı'ndan aktarma için yazıştık ve bana bir şirket önerdi****. Kişi başı 23TL'den Internet üzerinden Dalaman Havalimanı'ndan otele gidiş dönüşü ayarladım toplam 92TL'e. Bu aktarma işinin çok düzgün çalıştığını belirtmeliyim.

Öncelikle otelde yemekler çok güzeldi: Şaban Bey ve Hatice Hanım harikalar çıkarıyorlar...Rüzgar püfür eserken sahilde dut ağaçları altındaki şezlonglarda uzanmak çok hoştu. Bu ağaçlardan bayağı kara dut yedik! Güler yüzlü Şükrü'nün 17:00 gibi getirdiği atıştırmalık ve çaylar çok güzeldi. Derede yaşayan Pekin ördeklerine, ortalıkta dolaşan tavuklara ekmek parçaları atmak çok tatlıydı. Bize otele gelenler çoğunlukla kafa dinlemek isteyen çiftler veya küçük çocuklu aileler gibi geldi. Küçük çocuklu aileler mutfaktan vs özel isteklerde bulunabildikleri için rahat ediyorlar gibi duruyordu. Deniz suyu sıcak ve hafif dalgalı. Tek sorun sahilde taşlık bir şeridin olması...Sonuç olarak Yonca Lodge'u böyle sessiz, sakin tatil hedefleyen çiftlere veya küçük çocuklu ailelere tavsiye ediyorum. Zaten yapılan yorumlarda oldukça olumlu*****. Biz de kesinlikle bir daha gidecegiz!

* http://www.yoncalodge.com/
** http://www.nisanyan.net/otl_view.asp?id=608
*** Emre Karabacak: 0533 9240224, info@yoncalodge.com
**** https://www.koraltravel.com/transfer.asp
***** http://www.nisanyan.net/otl_comment.asp?otl_id=608

Abusing the Doxygen's "Test" Command

2009-07-21T14:28:00.000+03:00

According to the Doxygen documentation* the test command does the following:

\test { paragraph describing a test case }

Starts a paragraph where a test case can be described. The description will also add the test case to a separate test list. The two instances of the description will be cross-referenced. Each test case in the test list will be preceded by a header that indicates the origin of the test case.

Here, creating a separate list is a very nice feature! I think one can use the test command to have a list of all the tricky points which will be useful for maintenance: simply ask newcomers to generate the Doxygen documentation, study the "Test List" and learn all the cases by heart.

* http://www.stack.nl/~dimitri/doxygen/commands.html#cmdtest

Türk Hava Kuvvetleri Uçaklarını "Özgün Boyama"ya Başlamış

2009-06-15T22:33:00.000+03:00

Internet'de Türk uçak modelcilerinin forumlarına bakarken THK'nin Malatya 7. AJÜ'da konuşlu 172. Filo'daki emektar F-4E Phantom II'lerine "özgün boyama" uyguladığını gördüm. Tasarim Ömer Erkmen'e ait*: "En önemlisi, kuruluşundan bu yana, hava kuvvetlerimizde ilk defa kendimize özgü bir patern ile ucaklarımıza standart getirmiş olduk, inanın bizler kadar personelin moraline etkisi çok büyük oldu...". THK'nın USAF "Techical Order"ları dışına çıkmayı düşünmesine bir 241. Dönem Hava Uçak Bakım Yedeksubay olarak çok sevindim! Yunanistan'ın F-16C/D'leri ve İran'ın F-4D/E ve RF-4E'leri için kendi oluşturdukları boyama planlarını kullanmasına hep kıskanarak bakmıştım açıkcası...

Gerçi filo "geçici" olarak kapatılıyormuş: anladığım kadarıyla F-4E'leri yenilenecekmiş. Ayrıca yine Ömer Erkmen RF-4E'ler için "özgün" bir boyama yaratmış ve birliklerde deneme sonrası yönergeler oluşturulunca tam olarak kullanıma girecekmiş **:

Ayrıca Ömer Erkmen yenilenen T-38A'larımız için de "özgün" bir boyama geliştirmiş ***:

Galiba yenilemeden geçecek F-16C/D'lerimiz için de "özgün boyama" hazırlanacakmış! Bence başta Ömer Erkmen olmak üzere ilgili THK personeline teşekkür borçluyuz...

* 172. Filo "özgün boyama"ları

** RF-4E "özgün boyama"ları

*** T-38A "özgün boyama"ları

Kaplumbağa Terbiyecisi (1906)

2009-05-16T20:46:00.002+03:00

Prof. Dr. Edhem Eldem'in "Ressamlar, Kaplumbağalar, Tarihçiler..." * başlıklı yazısı Osman Hamdi Bey'in ünlü Kaplumbağa Terbiyecisi (1906) tablosu için yapılan yorumları "aşırı okuma" olarak nitelendiriyor. 2004 yılında Pera Müzesi tarafından 5TrilyonTL'e Erol Aksoy'dan satın alınmasıyla "yerli Mona Lisa" muamelesi görmeye başlayan tablo [1] sanat tarihçileri tarafından oldukça incelenmiş bir eser. Yazar, makalesinin başında Osman Hamdi konusunda çalışmaları olmasına rağmen sanat tarihçisi olmadığı için resimlerini yorumlamaktan çekindiğini belirtiyor ve "en büyük sıkıntılarımdan biri de bu tür yorumların biraz fazlaca rahat bir şekilde yapılıyor olmasıdır" diyor: "Bunu yapmak için de aslında Osman Hamdi Bey'in hiçbir yazılı ifadesine dayanmadan sadece resimlerde yer alan figürler, kompoziyon, konu, işleniş tarzı vs. üzerinden bu yorumlarını yapmaktadırlar."

Tablonun satışını takip eden aylarda Gazateci Emre Aköz "Aranızda hiç kaplumbağa tercbiyecisi gören var mı? Osman Hamdi Bey ve trilyonluk resimi" [2] başlıklı yazısında önemli bir soru sormuş: "Soru aklıma düştü: Osmanlı'da 'kaplumbağa terbiyeciliği' diye bir meslek, hüner var mıydı? Varsa kimler, nasıl icra ederdi...Peki acaba işin uzmanları bu konuda ne diyordu?" Edhem Eldem o zaman "muhtemelen bu sahnenin bir hayal ürünü olduğunu" söylemiş. Emre Aköz tarihçilerden "doğru dürüst" bir yanıt alamayınca "tarihçiliğimizin sırrını kendi kendine keşfetmişti: Belge veya bilgi yoksa yoruma kuvvet": "O zaman bunun 'simgesel anlamlarla yüklü' bir resim olduğunu söyleyebiliriz... Mesela Eczacıbaşı Sanal Müzesi'nde yer alan bir yorumda, Osman Hamdi'nin bu resmi yaparak, herhalde yavaş, miskin, tutucu çalışma arkadaşlarını hicvettiği yazılı."

Sanat tarihçilerinin yorumlarını özetlemeden önce bence ilginç bir biçimde Edhem Eldem Ekşi Sözlük'de bu tablo için yapılan yorumlara değiniyor. Burada yetersiz bilgisine rağmen her şeyi manalandırarak "ahkam kesen" "aydın" otorite figürüne dokundurmadan geçmiyor! Tablo yorumları için yazarın vardığı sonuç: "... mesele şu ki tarhçiler genellikle tablolardan hareketle Osman Hamdi Bey'i anlatmaya çalışıyor gibi gözükseler de aslında yaptıkları bunun tam tersi: Osman Hamdi'yi bir veri olarak alıp tablolarını o veriden hareketle okuyorlar...Osman Hamdi Bey'in fırçasından çıkıp da bütün bu ağır sembolizmi yüklediğimiz tablolardan herhangi birini Osman Hamdi'nin değil de başkasının, bir Batılının imzasıyla görmüş olsak da aynı şekilde yorumlar mıydık?...Metafor esastır, mana başattır, simge tabloyu yapıyor, gerisi teferruattır...Bu yüzdendir ki benim derdim aslında yorumlarla değil, ezici varlıklarıyladır. Bu mantığı aşırı ucuna kadar yürütürsek ...bir noktadan sonra tablolarına ihtiyaç kalmayacaktır veya daha da korkutucusu, yapmış olması gereken tabloları tesbit etmeye başlayacagız."

Sonrasında Edhem Eldem "kaplumbağa terbiyesi" konusuna geri dönüp "Google Book Search ve Fransız Milli Kütüphanesi'nin Gallica arama motoru"nu kullanarak Osman Hamdi Bey'in olası ilham kaynağını buluyor: "Nihayet işin sırrı çözülmüş oldu. Kaplumbağa terbiyesi diye bir sanat, Kaplumbağa terbiyecisi diye bir meslek vardır ve bunlara en azından on dokuzuncu yüzyılda Japonya'da rastlanabiliyordu...1869 yılında babası Edhem Paşa, Bağdat'da Midhat Paşa'nın maiyetinde bulunan oğlu Osman Hamdi'ye Le Tour de Monde'un o seneye ait ilk cildini yollamış, oğlu da bunu zevkle okumuştu. Söz konusu eserin 402. sayısında Japon kaplumbağa terbiyecisinin [3] gravürü yer almaktaydı...Artık galiba muhteşem Lale Devri'mizin "kapıkulu kaplumbağaları"nı rahat bırakmanın vakti gelmiş olsa gerek".

Edhem Eldem tablonun ilk adı olan "Kaplumbağalı Adam" başlığıyla uyumlu bir yorumu tercih ediyor ve "terbiye" yorumundan uzak duruyor: "Bundan çıkartacağımız bir sonuç da, Osman Hamdi Bey'in bir "mesaj" ressamından çok, esas olarak bir genre ressamı olduğu, dolayısıyla da asıl arzusunun hoş ve uyumlu bulduğu unsurları bir araya getirerek oluşturudğu kompoziyonların hayali de olsa bir yaşam anını yansıtmasını sağlayabilmek olduğudur." Bu arada Osman Hamdi Bey Edhem Eldem'in büyük büyük amcasıymış!

* Toplumsal Tarih, Mayıs 2009, s 20-30

[1] Wikipedia, tablonun Suna ve İnan Kıraç Vakfı tarafından 3.5 milyon USD'e Aralık 2004'de satın alındığını ve bu vakfın kurduğu Pera Müzesi'nde sergilendiğini yazıyor.

[2] Sabah, 28 Ağustos 2004

[3] Yazıda yapılan alıntılarda gravürdeki kaplumbağa terbiyecisinin "Koreli" olduğu söyleniyor.

gksudo'ed Terminal

2009-03-05T11:23:00.000+02:00

While working on the TeeVee project*, I compiled, installed and run the application as the "root" user. I needed new terminal tabs all the time and giving them root privileges was time consuming. Then I searched a bit and found that if I launch a terminal via gksudo, all the tabs created inherit the root privileges. So, I wrote the following script and run it happily afterwards:

gksudo.sh:

#! /bin/bash
gksudo gnome-terminal

I think this is a useful script. Obviously running commands with root privileges is a dangerous activity...

* I developed the code using a Ubuntu 8.04 installed Linux computer.

A Debug Macro for Xcode

2009-02-16T23:04:00.003+02:00

* Updated on 28 November 2011 for Xcode 4.2

I am a newcomer to the Xcode and I decided to check the debug means. Basically, I was looking for a macro to dump line number, file name and function name along with some output. However, I found only some "simple" debug classes. I think debug output should be done by macros. I checked the Apple documentation and found an interesting topic: Variadic Macros. They are introduced by the C99 standard. After a few attempts I decided that the following macro is good enough for me:

// dbg.h

// Created by oguz.kupusoglu@gmail.com on 15/2/2009.

#ifdef DEBUG

#define DBG(format, ...) NSLog(@"%d,%s,"format,__LINE__,__FUNCTION__,##__VA_ARGS__);

#define DBG_CALLED DBG("called")

#else

#define DBG(format, ...)

#define DBG_CALLED

#endif

#define LOG(format, ...) NSLog(@"%d,%s,"format,__LINE__,__FUNCTION__,##__VA_ARGS__);

#define LOG_CALLED LOG("called")

Note that DBG_CALLED is a helper define which is useful for following the callstack. I ignored the file name, i.e. __FILE__, as the method name being in the [class method] format gives a hint of the file in question due to naming files after the class names convention. Certainly one can add __FILE__ at the expense of extra overhead. Sample usage and output as received from the Console which is accessed from the "View/Debug Area/Activate Console" option of the Xcode are below:

-(void) viewWillAppear:(BOOL)animated

{

DBG_CALLED

DBG("view frame\n"

"origin x:|%.0f| y:|%.0f|\n"

"width:|%.0f| height:|%.0f|\n",

self.view.frame.origin.x, self.view.frame.origin.y,

self.view.frame.size.width, self.view.frame.size.height)

DBG("year:|%d|", 2009)

DBG("updated")

[super viewWillAppear:animated];

}

...] 69,-[MyViewController viewWillAppear:],called

...] 75,-[MyViewController viewWillAppear:],view frame

origin x:|0| y:|20|

width:|768| height:|1004|

...] 77,-[MyViewController viewWillAppear:],year:|2009|

...] 79,-[MyViewController viewWillAppear:],updated

Note that the DEBUG define is set via the "PROJECT/Build Settings" option. Go to "... Preprocessing" section and add the define "DEBUG" to the "Debug" subsection.

Finally, I think "Product/Generate Output\Generate Preprocessed File" is a good option as it gives the preprocessor output of the selected file. For example the above DBG() macros are expanded as below:

-(void) viewWillAppear:(BOOL)animated

{

NSLog(@"%d,%s,""called",69,__FUNCTION__);

NSLog(@"%d,%s,""view frame\n" "origin x:|%.0f| y:|%.0f|\n" "width:|%.0f| height:|%.0f|\n",75,__FUNCTION__, self.view.frame.origin.x, self.view.frame.origin.y, self.view.frame.size.width, self.view.frame.size.height);

NSLog(@"%d,%s,""year:|%d|",77,__FUNCTION__, 2009);

NSLog(@"%d,%s,""updated",79,__FUNCTION__);

[super viewWillAppear:animated];

}

Note that when there is no variable argument, "##" removes the trailing comma! Just excellent...

Issız Adam

2009-02-08T15:23:00.006+02:00

Bu Çağan Irmak filmini* 7 Şubat 2009 Cumartesi günü seyrettik. Öykü yeni değil: hayatının kadını karşısına çıktığında bağlanmaktan korktuğu için onu terkeden bir adamın, yani Ada ve Alper'in öyküsü. Ayrıca filmdeki karakterler çok tuzu kuru, bohem hayatlar sürdürüyorlar. Ama oyuncuların sevimliliği, "Anne"nin kattığı gerçekçilik ve duygu sömürüsü düzeyinde duyguları yoğunlaştırmayı başaran yönetmen durumu kurtarıyor. Filmde Ada'nın kendisine asılan Alper'e kahve bardağını boşaltması, Ada'nın Alper'den ayrıldıktan sonra Alper'in annesinin yanına gitmesi ve son sahnede karşılaşmaları ve "Anlamazdın Anlamazdın" ile filmin bitişi oldukça hoş.

* http://www.imdb.com/title/tt1322930

Introduction to MacBook

2009-02-08T15:09:00.000+02:00

I bought a MacBook On 28 January 2009 from the Pupa at IstinyePark. My first impression is that it is very well designed! I think the Apple Key, i.e. "cmd" key, replaces the Control Key on the Windows computers. And, there is no "right" mouse key: in order to open a context menu the user needs to press "cntrl" key. However, I think having no "fullscreen" windows is a problem! Plus, it is not easy to see the open windows: F3 keys shows them and CMD+TAB selects windows sequentially. Overall I think as time goes by I will like the MacBook!