{5} Assigned, Active Tickets by Owner (Full Description) (8 matches)

Les fonctions sha1 et md5 attendent n'importe quel type sérialisable en entrée. Or lorsqu'on lui passe un String, on s'attend à ce que ce soit le contenu de la chaine qui soit utilisé pour le calcul du SHA1 ou du MD5. Or il se trouve que c'est l'objet String en entier qui est calculé.

C'est donc source d'erreur évidente, et très difficile à prévenir. Or pour le cas particulier du String, signer l'objet complet ou signer son contenu, c'est aussi pertinent dans un cas comme dans l'autre. C'est donc absolument équivalent.

Donc pour simplifier et réduire les risques, il faudrait directement dans predifined.anubis créer des versions surchargées pour le type String ne fonctionnant que sur le contenu.

Could be a nice code example :)
Sadly some arithmetic debugging is still needed :(

// Spigot by Jeremy Gibbons, using William Gosper formula

public define Int
   div(Int a,Int b) 
     =
   if a / b is 
     {
     failure    then 0,
     success(d) then if d is (q,r) then q
     }.

global define One
  pi_gosper_gibbons(List(String) args)
  =
  ( (Int q,Int r,Int t,Int i) |-g-> 
    with
    u = 3*(3*i+1)*(3*i+2),
    y = div(q*(27*i-12)+5*r,5*t),
    print(abs_to_decimal(y));
    g(10*q*i*(2*i-1),10*u*(q*(5*i-2)+r-y*t),t*u,i+1);
    unique
  )
  (1,180,60,2).

As standard library and functions or types that compose it aren't yet perfectly well designed, and name changes can be frequent, adding a keyword 'obsolete' (or any thing like this) could be a great help.

This keyword does nothing else than producing a warning during compile time, just to remember to not use this function.

A variation of this could be the keyword : obsolete(new_function)

With this, the compiler can produce a very useful warning, telling which function to use instead of this one.

The keyword could be inserted into function or type definition like this :

public define obsolete(new_function_name) ReturnType
  old_function_name
  (
    ...
  ) =
  <function body>.

Or maybe better (as we can suppose that 'obsolete' functions or type are always public ones):

obsolete(new_function_name) define ReturnType
  old_function_name
  (
    ...
  ) =
  <function body>.

which made automatically this function public but obsolete.

Private function can always be easily renamed, so there is no need to mark them as obsolete.

I report this not so serious bug for documentation only (it could eventually puzzle some beginner). As trivial as it seems patching it probably involves tweaking the lexical analyser, quite not a really exciting thing to do.

type Yell : woow.

If no newline (end of file just following the dot) then i get this error:

(line 1, column 18) Error E111:    Premature end of file within a paragraph.