File: BUGS

package info (click to toggle)
kaya 0.4.2-4
  • links: PTS
  • area: main
  • in suites: lenny
  • size: 4,448 kB
  • ctags: 1,694
  • sloc: cpp: 9,536; haskell: 7,461; sh: 3,013; yacc: 910; makefile: 816; perl: 90
file content (39 lines) | stat: -rw-r--r-- 1,847 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
Currently known bugs (09/06/08  v 0.4.2)

Major (i.e. must be fixed for next version):

* Problem with documentation generation on Mac

Minor:

* Functions which return Void behave incorrectly in HOFs where the
  function argument is polymorphic in its return type.
* 'var' arguments do not work with partial function application.
* Function applications need to be on names, rather than complex
  expressions. This should be more general, eg f.a[5](args) should be allowed.
  (5/2/05 - bit better now; as long as it's not a Void function, you
  can apply any typed expression).
* Attempting to marshal Foreign Ptrs should be an error - need a
  built-in function table for Ptr.
* The compiler should attempt to report as many errors as possible
  (might be tricky). 
* Should be a warning if module name doesn't correspond with filename,
  as module chasing won't work in that case. Not a problem for
  programs or webapps however.
* Unhelpful error if main/Default/etc has the wrong type
* Dependency chasing and recompiling doesn't work with include()d
  parts of modules, and nor does documentation generation.
* Overloading functions with the same name and parameters but
  different return type compiles in the kayac stage but not in gcc
  stage
* Overloading functions with different parameters types where the
  difference is based on type variables (e.g. Int(a,b,String) and
  Int(String,a,b(a))) gives functions with the same C name.
* Overloading functions where the parameters of one type are a subset of
  the parameters of the other fails.
* Error report for adding the same constructor twice in a case statement is
  unhelpful.
* Building a .k file in a different directory doesn't generate
  -xmldocs correctly.
* Pattern matcher can be very slow with some data types.
* import public gives odd information in exception backtraces