Campeonato Português de Futebol 1971/1972







Primeira Liga |



Classificação |


{{Futebol/Classificação/16|
| SL Benfica | 55 | 30
| 26 | 3 | 1 | 81-16
| 13 | 2 | 0 | 43-6
| 13 | 1 | 1 | 38-10
| VFC Setúbal | 45 | 30
| 17 | 11 | 2 | 62-16
| 11 | 2 | 2 | 41-6
| 6 | 9 | 0 | 21-10
| Sporting CP | 43 | 30
| 17 | 9 | 4 | 51-26
| 11 | 2 | 2 | 29-11
| 6 | 7 | 2 | 22-15
| GD CUF | 37 | 30
| 12 | 13 | 5 | 43-28
| 8 | 5 | 2 | 31-15
| 4 | 8 | 3 | 12-13
| FC Porto | 33 | 30
| 13 | 7 | 10 | 51-32
| 7 | 3 | 5 | 28-16
| 6 | 4 | 5 | 23-16
| VSC Guimarães | 30 | 30
| 11 | 8 | 11 | 49-47
| 7 | 5 | 3 | 31-18
| 4 | 3 | 8 | 18-29
| CF Belenenses | 29 | 30
| 11 | 7 | 12 | 35-33
| 7 | 3 | 5 | 19-13
| 4 | 4 | 7 | 16-20
| FC Barreirense | 27 | 30
| 11 | 5 | 14 | 34-46
| 7 | 3 | 5 | 23-17
| 4 | 2 | 9 | 11-29
| SC Farense | 25 | 30
| 9 | 7 | 14 | 34-48
| 9 | 4 | 2 | 27-18
| 0 | 3 | 12 | 7-30
| Atlético CP | 25 | 30
| 8 | 9 | 13 | 35-52
| 5 | 7 | 3 | 21-20
| 3 | 2 | 10 | 14-32
| Boavista FC | 24 | 30
| 7 | 10 | 13 | 28-46
| 6 | 5 | 4 | 19-14
| 1 | 5 | 9 | 9-32
| UFCI Tomar | 23 | 30
| 9 | 5 | 16 | 25-42
| 7 | 4 | 4 | 18-14
| 2 | 1 | 12 | 7-28
| SC Beira Mar | 23 | 30
| 7 | 9 | 14 | 29-51
| 4 | 6 | 5 | 19-21
| 3 | 3 | 9 | 10-30
| Leixões SC | 21 | 30
| 7 | 7 | 16 | 26-51
| 4 | 4 | 7 | 11-16
| 3 | 3 | 9 | 15-35
| Académica | 21 | 30
| 7 | 7 | 16 | 29-38
| 5 | 4 | 6 | 18-16
| 2 | 3 | 10 | 11-22
| FC Tirsense | 19 | 30
| 6 | 7 | 17 | 26-66
| 6 | 3 | 6 | 18-21
| 0 | 4 | 11 | 8-45
|


Fonte: Futebol Português em Números



-

Popular posts from this blog

Contact image not getting when fetch all contact list from iPhone by CNContact

Image
up vote 0 down vote favorite I know this question already asked but not getting solution. From this code I will get all the information from the contact but image not found when open vcf files on mac os, also not getting when share this file. I use this stackoverflow link here but It's not help full. var contacts = [CNContact]() let keys = [CNContactVCardSerialization.descriptorForRequiredKeys() ] as [Any] let request = CNContactFetchRequest(keysToFetch: keys as! [CNKeyDescriptor]) do { try self.contactStore.enumerateContacts(with: request) { (contact, stop) in // Array containing all unified contacts from everywhere contacts.append(contact) } } catch { print("unable to fetch contacts") } do { let data = try
Read more

count number of partitions of a set with n elements into k subsets

Image
up vote 6 down vote favorite 1 This program is for count number of partitions of a set with n elements into k subsets I am confusing here return k*countP(n-1, k) + countP(n-1, k-1); can some one explain what is happening here? why we are multiplying with k? NOTE->I know this is not the best way to calculate number of partitions that would be DP // A C++ program to count number of partitions // of a set with n elements into k subsets #include<iostream> using namespace std; // Returns count of different partitions of n // elements in k subsets int countP(int n, int k) { // Base cases if (n == 0 || k == 0 || k > n) return 0; if (k == 1 || k == n) return 1; // S(n+1, k) = k*S(n, k) + S(n, k-1) return k*countP(n-1, k) + countP(n-1, k-1); } // Driver program int ma
Read more

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Image
0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{
Read more