1992 Japan Football League
Statistics of Japan Football League in the 1992 season.
First Division
| Pos | Club | Pts | W | D | L | GF | GA | GD | Notes |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Yamaha Motors | 44 | 13 | 5 | 0 | 37 | 6 | ＋31 | |
| 2 | Hitachi | 40 | 12 | 4 | 2 | 37 | 19 | ＋18 | |
| 3 | Fujita Industries | 31 | 9 | 4 | 5 | 37 | 22 | +15 | |
| 4 | Yanmar Diesel | 24 | 7 | 3 | 8 | 23 | 19 | ＋4 | |
| 5 | Toshiba | 23 | 6 | 5 | 7 | 30 | 29 | +1 | |
| 6 | Fujitsu | 20 | 5 | 5 | 8 | 19 | 27 | -8 | |
| 7 | Tokyo Gas | 20 | 5 | 5 | 8 | 22 | 34 | －12 | |
| 8 | Otsuka Pharmaceutical | 18 | 4 | 6 | 8 | 17 | 29 | －12 | |
| 9 | Honda | 16 | 4 | 4 | 10 | 19 | 36 | －17 | Relegated to Second Division |
| 10 | Nippon Kokan | 11 | 2 | 5 | 11 | 12 | 32 | －20 |
Second Division
Seino Unyu and Osaka Gas had been promoted automatically after winning the Regional Playoffs.
| Pos | Club | Pts | W | D | L | GF | GA | GD | Notes |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Chuo Bohan | 38 | 12 | 2 | 4 | 46 | 21 | ＋25 | Promoted to First Division |
| 2 | Kyoto Shiko Club | 37 | 11 | 4 | 3 | 39 | 17 | ＋22 | |
| 3 | Kawasaki Steel | 35 | 11 | 2 | 5 | 32 | 17 | +15 | |
| 4 | Cosmo Oil | 30 | 9 | 3 | 6 | 26 | 21 | ＋5 | |
| 5 | Kofu Club | 28 | 9 | 1 | 8 | 26 | 29 | －3 | |
| 6 | NTT Kanto | 22 | 5 | 7 | 6 | 24 | 20 | ＋4 | |
| 7 | Seino Unyu | 19 | 4 | 7 | 7 | 20 | 29 | －9 | |
| 8 | Toho Titanium | 14 | 2 | 8 | 8 | 9 | 19 | －10 | |
| 9 | Tanabe Pharmaceutical | 14 | 3 | 5 | 10 | 17 | 32 | －15 | Relegated to Regional Leagues |
| 10 | Osaka Gas | 12 | 3 | 3 | 12 | 14 | 48 | －34 |
gollark: Anyway, more generally, you need to know the idioms of a language to know if someone *else* does.
gollark: Since basically all the JS I've seen uses the second one.
gollark: If I saw the top one (and it wasn't in an event like this where everyone will second-guess everything) I would assume that it was written by someone who used C(++) a lot.
gollark: e.g. if you have some JS code, and you see that the author used ```javascriptfunction deployBee(){}```brackets and not```javascriptfunction deployBee() {}```ones, you need to know a bit about what JS code normally looks like to infer anything like that.
gollark: I don't think so. Things like variable names and formatting are *fairly* obvious, although you may need to read a decent sample of code in language X to learn what people generally do there regarding those, but stuff like what constructs are generally used for tasks in language X are not.
References
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.