Use native methods judiciously. (Item 54,55,56) - презентация, доклад, проект скачать

Нажмите для полного просмотра!

Use native methods judiciously. (Item 54,55,56), слайд №1

Use native methods judiciously. (Item 54,55,56), слайд №2

Use native methods judiciously. (Item 54,55,56), слайд №3

Use native methods judiciously. (Item 54,55,56), слайд №4

Use native methods judiciously. (Item 54,55,56), слайд №5

Use native methods judiciously. (Item 54,55,56), слайд №6

Use native methods judiciously. (Item 54,55,56), слайд №7

Use native methods judiciously. (Item 54,55,56), слайд №8

Use native methods judiciously. (Item 54,55,56), слайд №9

Use native methods judiciously. (Item 54,55,56), слайд №10

Use native methods judiciously. (Item 54,55,56), слайд №11

Use native methods judiciously. (Item 54,55,56), слайд №12

Use native methods judiciously. (Item 54,55,56), слайд №13

Use native methods judiciously. (Item 54,55,56), слайд №14

Use native methods judiciously. (Item 54,55,56), слайд №15

Содержание ▲

Вы можете ознакомиться и скачать презентацию на тему Use native methods judiciously. (Item 54,55,56). Доклад-сообщение содержит 15 слайдов. Презентации для любого класса можно скачать бесплатно. Если материал и наш сайт презентаций Mypresentation Вам понравились – поделитесь им с друзьями с помощью социальных кнопок и добавьте в закладки в своем браузере.

Слайды и текст этой презентации

Слайд 1

Описание слайда:

Item 54: Use native methods judiciously

Слайд 2

Описание слайда:

Disadvantages of native methods: Not save – memory corruption errors may occur Platform dependent – native methods are less portable More difficulties with debugging Worse performance doing a small amount of work – consume some resources for going into and out of native code

Слайд 3

Описание слайда:

Use as little native code as possible

Слайд 4

Описание слайда:

Strive to write good programs rather than fast ones Don’t sacrifice sound architectural principles for performance

Слайд 5

Описание слайда:

Strive to avoid design decisions that limit performance Components interacting between modules and with the outside world are difficult to change.

Слайд 6

Описание слайда:

Consider the performance consequences of your API design decisions Mutable public class – may require a lot of needles defensive coping Inheritance – ties class with its parent and may have limits on the performance of superclass Interfaces – allow to create faster implementation in the future

Слайд 7

Описание слайда:

Don’t warp API to achieve good performance Problems with performance may go away in future releases, bad API – never

Слайд 8

Описание слайда:

Measure performance before and after each attempted optimization Effect can be measurable or even negative

Слайд 9

Описание слайда:

Java doesn’t have a strong performance model There is a gap between what the programmer writes and what the CPU executes

Слайд 10

Описание слайда:

Item 56: Adhere to generally accepted naming conventions

Слайд 11

Описание слайда:

Packages Components of package names should consist of lowercase alphabetic characters and, rarely digits. Components should be short, generally eight or fewer characters. Meaningful abbreviations are encouraged (For example, util rather than utilities)

Слайд 12

Описание слайда:

Classes and interfaces Abbreviations are to be avoided, except for acronyms and certain common abbreviations like max and min. Acronyms can be either uppercase or have only their first letter capitalized (The second is better. HTTPURL or HttpUrl)

Слайд 13

Описание слайда:

Method and field names The same as classes’ names but the firstLetterShouldBeLowercase. If constant – UPPERCASE_WORDS_SEPARETED_WITH_UNDERSCORE

Слайд 14

Описание слайда:

Local variable The same as members’ names but abbreviations are available

Слайд 15

Описание слайда:

Type parameter names T for an arbitrary type E for the element type of a collection K and V for the key and value types of a map X for an exception A sequence of arbitrary types can be T, U, V or T1, T2, T3.