## 2.动态加载

1. Java程序在运行时并不一定被完全加载，只有当发现该类还没有加载时，才去本地或者远程查找类的.clsss文件并验证和加载。
2. 当程序创建了第一个对类的静态成员(如类的静态变量、静态方法、构造方法-构造方法也是静态的)的引用时，才会加载该类。Java的这个特性叫做：动态加载

• 初始化(initialization)：首先执行静态初始化块static{}，初始化静态变量，执行静态方法(如构造方法)

### 链接

Java在加载了类之后，需要进行链接的步骤，链接简单地说，就是讲已经加载的Java二进制代码组合刀JVM运行状态中去。它包括三个步骤：

1. 验证(verification)：验证是保证二进制字节码在结构上的正确性，具体来说，工作包括检测类型正确性，接入属性正确性(public、private)，检查final Class没有被继承，检查静态变量的正确性等
2. 准备(perparation)：准备阶段主要是创建静态域，分配空间，给这些域设置默认值。需要注意的是两点：一个是在准备阶段不会执行任何代码，仅仅是设置默认值。二是这些默认值是这样分配的，原生类型全部设为0，如：float 0f，int 0，boolean 0，其他引用类型为NULL
3. 解析(resolution)：解析的过程就是对类中的接口、类、方法、变量的符号引用进行解析并定位，解析成直接引用(符号引用就是编码使用字符串标识某个变量、接口的位置，直接引用就是根据符号引用翻译出来的地址),并保证这些类被正确得找到。解析的过程可能导致其他的类被加载。需要注意的是，根据不同的解析策略，这一步不一定是必须的，有些解析策略在解析时把所有引用解析，这是early relolution，要求所有引用都必须存在。还有一种策略是late relolution，这也是Oracle jdk所采取的策略，即在类只有被引用了，还没有被真正用到时，并不进行解析，只有当真正用到了，才去加载和解析这个类

### 初始化

static{}是在第一次初始化时执行的，且只执行一次，用下面的代码可以判定出来：

``````public class Toy {
private String name;

public static final int price = 10;

static {
System.out.println("initializing");
}

public Toy() {
System.out.println("building");
}

public Toy(String name) {
this.name = name;
}
}
``````

``````Class c = Class.forName("com.pescod.entity.Toy");
``````

initializing

1. 创建类的实例
2. 访问某个类或者接口的静态变量，或者对静态变量赋值(如果访问的是静态编译时常量(即编译时可以确定值的常量)不会导致类的初始化)
3. 调用类中的静态方法
4. 反射(Class.forName(“xxx.xxx”))
5. 初始化一个类的子类(相当于对父类的主动使用)，不过直接通过子类引用父类元素，不会引起子类的初始化(参考实例6)
6. 被Java虚拟机标明为启动类的类(包含main方法)

#### 示例

##### 示例1

``````public class Toy {

//静态子句，只在类第一次被加载并初始化时执行一次，而且只执行一次
static {
System.out.println("initializing");
}

//构造方法，在每次声明新对象时加载
public Toy() {
System.out.println("building");
}
}
``````

##### 示例2

``````//获得类（注意，需要使用含包名的全限定名）
Class cc = Class.forName("Toy");
//相当于new一个对象，但Gum类必须有默认构造方法（无参)
Toy toy=(Toy)cc.newInstance();
``````
##### 示例3

``````public class TestToy {
public static void main(String[] args) {
Class c = Toy.class; // 不会输出任何值
}
}
``````

##### 示例4

``````static int a;
final int b;
static final int c = ClassInitialization.rand.nextInt(100);
static final int d;
static {
d = 5;
}
``````
##### 示例5

static块的本质，注意下面的代码

``````class StaticBlock {
static final int c = 3;
static final int d;
static int e = 5;
static {
d = 5;
e = 10;
System.out.println("Initializing");
}

StaticBlock() {
System.out.println("Building");
}
}

public class StaticBlockTest {
public static void main(String[] args) {
System.out.println(StaticBlock.c);
System.out.println(StaticBlock.d);
System.out.println(StaticBlock.e);
}
}

``````

3
Initializing
5
10

``````class StaticBlock {
static final int d;
static int e;
static {
e=5;
}

static {
d = 5;
e = 10;
System.out.println("Initializing");
}

StaticBlock() {
System.out.println("Building");
}
}
``````

``````class StaticBlock {
static {
d = 5;
e = 10;
System.out.println("Initializing");
}

static final int d;

static int e = 5;

StaticBlock() {
System.out.println("Building");
}
}
``````

##### 示例6

``````class B {
static int value = 100;
static {
System.out.println("Class B is initialized");// 输出
}
}

class A extends B {
static {
System.out.println("Class A is initialized"); // 不输出
}
}

public class SuperClassTest {
public static void main(String[] args) {
System.out.println(A.value);// 输出100
}
}
``````

Class B is initialized
100

# MacDown

Hello there! I’m MacDown, the open source Markdown editor for OS X.

Let me introduce myself.

## Markdown and I

Markdown is a plain text formatting syntax created by John Gruber, aiming to provide a easy-to-read and feasible markup. The original Markdown syntax specification can be found here.

MacDown is created as a simple-to-use editor for Markdown documents. I render your Markdown contents real-time into HTML, and display them in a preview panel.

I support all the original Markdown syntaxes. But I can do so much more! Various popular but non-standard syntaxes can be turned on/off from the Markdown preference pane.

You can specify extra HTML rendering options through the Rendering preference pane.

You can customize the editor window to you liking in the Editor preferences pane:

You can configure various application (that’s me!) behaviors in the General preference pane.

## The Basics

Before I tell you about all the extra syntaxes and capabilities I have, I’ll introduce you to the basics of standard markdown. If you already know markdown, and want to jump straight to learning about the fancier things I can do, I suggest you skip to the Markdown preference pane. Lets jump right in.

### Line Breaks

To force a line break, put two spaces and a newline (return) at the end of the line.

• This two-line bullet
won’t break

• This two-line bullet
will break

Here is the code:

``````* This two-line bullet
won't break

* This two-line bullet
will break
``````

### Strong and Emphasize

Strong: `**Strong**` or `__Strong__` (Command-B)
Emphasize: `*Emphasize*` or `_Emphasize_`1 (Command-I)

``````Header 1
========

--------
``````

or

``````# Header 1
``````

#### Inline

Just put angle brackets around an email and it becomes clickable: uranusjr@gmail.com
`<uranusjr@gmail.com>`

Same thing with urls: http://macdown.uranusjr.com
`<http://macdown.uranusjr.com>`

Perhaps you want to some link text like this: Macdown Website
`[Macdown Website](http://macdown.uranusjr.com "Title")` (The title is optional)

#### Reference style

Sometimes it looks too messy to include big long urls inline, or you want to keep all your urls together.

Make a link `[a link][arbitrary_id]` then on it’s own line anywhere else in the file:
`[arbitrary_id]: http://macdown.uranusjr.com "Title"`

If the link text itself would make a good id, you can link like this `[like this][]`, then on it’s own line anywhere else in the file:
`[like this]: http://macdown.uranusjr.com`

### Images

#### Inline

`![Alt Image Text](path/or/url/to.jpg "Optional Title")`

#### Reference style

`![Alt Image Text][image-id]`
on it’s own line elsewhere:
`[image-id]: path/or/url/to.jpg "Optional Title"`

### Lists

• Lists must be preceded by a blank line (or block element)
• Unordered lists start each item with a `*`
• `-` works too
• Indent a level to make a nested list
1. Ordered lists are supported.
2. Start each item (number-period-space) like `1.`
3. It doesn’t matter what number you use, I will render them sequentially
4. So you might want to start each line with `1.` and let me sort it out

Here is the code:

``````* Lists must be preceded by a blank line (or block element)
* Unordered lists start each item with a `*`
- `-` works too
* Indent a level to make a nested list
1. Ordered lists are supported.
2. Start each item (number-period-space) like `1. `
42. It doesn't matter what number you use, I will render them sequentially
1. So you might want to start each line with `1.` and let me sort it out
``````

### Block Quote

Angle brackets `>` are used for block quotes.
Technically not every line needs to start with a `>` as long as
there are no empty lines between paragraphs.
Looks kinda ugly though.

Block quotes can be nested.

Multiple Levels

Most markdown syntaxes work inside block quotes.

Here is the code:

``````> Angle brackets `>` are used for block quotes.
Technically not every line needs to start with a `>` as long as
there are no empty lines between paragraphs.
> Looks kinda ugly though.
> > Block quotes can be nested.
> > > Multiple Levels
>
> Most markdown syntaxes work inside block quotes.
>
> * Lists
> * Etc.
``````

### Inline Code

`Inline code` is indicated by surrounding it with backticks:
``Inline code``

If your `code has `backticks`` that need to be displayed, you can use double backticks:
```Code with `backticks` ``` (mind the spaces preceding the final set of backticks)

### Block Code

If you indent at least four spaces or one tab, I’ll display a code block.

``````print('This is a code block')
print('The block must be preceded by a blank line')
print('Then indent at least 4 spaces or 1 tab')
print('Nesting does nothing. Your code is displayed Literally')
``````

I also know how to do something called Fenced Code Blocks which I will tell you about later.

### Horizontal Rules

If you type three asterisks `***` or three dashes `---` on a line, I’ll display a horizontal rule:

## The Markdown Preference Pane

This is where I keep all preferences related to how I parse markdown into html.

### Document Formatting

The Smartypants extension automatically transforms straight quotes (`"` and `'`) in your text into typographer’s quotes (`“`, `”`, `‘`, and `’`) according to the context. Very useful if you’re a typography freak like I am. Quote and Smartypants are syntactically incompatible. If both are enabled, Quote takes precedence.

### Block Formatting

#### Table

This is a table:

Content Cell Content Cell
Content Cell Content Cell

You can align cell contents with syntax like this:

Left Aligned Center Aligned Right Aligned
col 3 is some wordy text \$1600
col 2 is centered \$12
zebra stripes are neat \$1

The left- and right-most pipes (`|`) are only aesthetic, and can be omitted. The spaces don’t matter, either. Alignment depends solely on `:` marks.

#### Fenced Code Block

This is a fenced code block:

``````print('Hello world!')
``````

You can also use waves (`~`) instead of back ticks (```):

``````print('Hello world!')
``````

You can add an optional language ID at the end of the first line. The language ID will only be used to highlight the code inside if you tick the Enable highlighting in code blocks option. This is what happens if you enable it:

I support many popular languages as well as some generic syntax descriptions that can be used if your language of choice is not supported. See relevant sections on the official site for a full list of supported syntaxes.

### Inline Formatting

The following is a list of optional inline markups supported:

Option name Markup Result if enabled
Intra-word emphasis So A*maz*ing So Amazing
Strikethrough \~~Much wow\~~ Much wow
Underline 2 _So doge_ So doge
Quote 3 \”Such editor\” Such editor
Highlight \==So good\== So good
Superscript hoge\^(fuga) hogefuga
Footnotes [\^4] and [\^4]: 4 and footnote 4

## The Rendering Preference Pane

This is where I keep preferences relating to how I render and style the parsed markdown in the preview window.

### CSS

You can choose different css files for me to use to render your html. You can even customize or add your own custom css files.

### Syntax Highlighting

You have already seen how I can syntax highlight your fenced code blocks. See the Fenced Code Block section if you haven’t! You can also choose different themes for syntax highlighting.

### TeX-like Math Syntax

I can also render TeX-like math syntaxes, if you allow me to.5 I can do inline math like this: \( 1 + 1 \) or this (in MathML):

$1+1$

, and block math:

\[
A^T_S = B
\]

or (in MathML)

$A S T$
=
B

1. [x] I can render checkbox list syntax
• [x] I support nesting
• [x] I support ordered and unordered lists
2. [ ] I don’t support clicking checkboxes directly in the html window

### Jekyll front-matter

If you like, I can display Jekyll front-matter in a nice table. Just make sure you put the front-matter at the very beginning of the file, and fence it with `---`. For example:

``````---
title: "Macdown is my friend"
date: 2014-06-06 20:00:00
---
``````

### Render newline literally

Normally I require you to put two spaces and a newline (aka return) at the end of a line in order to create a line break. If you like, I can render a newline any time you end a line with a newline. However, if you enable this, markdown that looks lovely when I render it might look pretty funky when you let some other program render it.

## The General Preferences Pane

This is where I keep preferences related to application behavior.

The General Preferences Pane allows you to tell me how you want me to behave. For example, do you want me to make sure there is a document open when I launch? You can also tell me if I should constantly update the preview window as you type, or wait for you to hit `command-R` instead. Maybe you prefer your editor window on the right? Or to see the word-count as you type. This is also the place to tell me if you are interested in pre-releases of me, or just want to stick to better-tested official releases.

## The Editor Preference Pane

This is where I keep preferences related to the behavior and styling of the editing window.

### Styling

My editor provides syntax highlighting. You can edit the base font and the coloring/sizing theme. I provided some default themes (courtesy of Mou’s creator, Chen Luo) if you don’t know where to start.

You can also edit, or even add new themes if you want to! Just click the Reveal button, and start moving things around. Remember to use the correct file extension (`.styles`), though. I’m picky about that.

I offer auto-completion and other functions to ease your editing experience. If you don’t like it, however, you can turn them off.

## Hack On

That’s about it. Thanks for listening. I’ll be quiet from now on (unless there’s an update about the app—I’ll remind you for that!).

Happy writing!

``````public class Toy{
private String name;
public static final int price = 10;

static{
System.out.println("initializing");
}
Toy(){
System.out.println("Building");
}
public static void main(String[] args) {
try{
//Class c = Class.forName("Toy");
Class c = Toy.class;
}catch(Exception e){
System.out.println(e);
}

//c.newInstance();
}
}

``````

1. If Underlines is turned on, `_this notation_` will render as underlined instead of emphasized
2. If Underline is disabled `_this_` will be rendered as emphasized instead of being underlined.
3. Quote replaces literal `"` characters with html `<q>` tags. Quote and Smartypants are syntactically incompatible. If both are enabled, Quote takes precedence. Note that Quote is different from blockquote, which is part of standard Markdown.
4. You don’t have to use a number. Arbitrary things like `[^footy note4]` and `[^footy note4]:` will also work. But they will render as numbered footnotes. Also, no need to keep your footnotes in order, I will sort out the order for you so they appear in the same order they were referenced in the text body. You can even keep some footnotes near where you referenced them, and collect others at the bottom of the file in the traditional place for footnotes.
5. Internet connection required.