Skip to content
This repository has been archived by the owner on Apr 23, 2020. It is now read-only.

Validation of all “complexNyms” #13

Merged
merged 7 commits into from
Mar 7, 2012
Merged

Validation of all “complexNyms” #13

merged 7 commits into from
Mar 7, 2012

Conversation

RubixR4
Copy link
Collaborator

@RubixR4 RubixR4 commented Mar 6, 2012

Need almost kanban validation for all complex relations :

  • Parser algorithm : ok
  • Parser implementation : ok
  • API : ok
  • API documentation : ok
  • Parser documentation : ok
  • JUnit tests : ok
  • Scalable verification : still in progress

You can pull the commit n° 73f0ede to check only the relations hyponyms and meronyms.

@@ -42,6 +42,12 @@ import info.bliki.wiki.model.WikiModel;
private int definitionCount = 0;
private int definitionDepth = -1; // the depth is the number of sharps (#) in front of a definition, minus one (that's optimization to have only one substraction for the 0-based indexed list). So, to trigger comparisons, we need to be negative.

private Vector<Word> complexNyms; // Used for hyponyms, hyperonyms, holonyms, and meronyms
private int complexDepth = 1; // Used to calculate the depth of the list (number of '*')
private boolean complexAlgoDirection; // Used for complexNym algorithm :
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Préférer la documentation par /** quand les informations pourraient être incluses dans une doc externe. Les commentaires // sont à n'utiliser que pour les infos niveau programmeur, i.e. quand on a les “mains dans le cambouis”.

(c'est pas juste pour l'idée, c'est parce que la doc est réellement générée à partir des blocs /** et rien d'autre)

(j'ai corrigé ça dans mon dernier commit, faire un pull avant de corriger quoi que ce soit)

@MattiSG MattiSG merged commit e8361d6 into master Mar 7, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants