[Aldor-l] Bug in README.building

[Bill Page]

Ralf,

I think it is great you are looking at these issues. I also noticed
this and several more problems in the README and other files but I
haven't done anything yet because I have been waiting for aldor.org to
announce their policy for commits to the svn repository. Ideally
solving problems like these should be a simple matter of you making
the changes locally and then doing a 'svn commit'. I hope that this
can be resolved soon.

But in lieu of that, perhaps it would be best to at least submit
patches, i.e. make the changes locally in your copy of the repository
and then post a patch to the email list created via

  svn diff

------

On another related subject, I think that the need to manually edit
'makefile.globals' is a serious problem. This should be eliminated as
soon as possible by the introduction of a ./configure step. As far as
I can see there is no reason for the source release of Aldor to differ
from "standard practice" in other open source software, so we should
be moving towards a GNU autoconf-style build as soon as possible.

Regards,
Bill Page.

On 9/25/07, Ralf Hemmecke <ralf at hemmecke.de> wrote:
> 6.  Test that the compiler is working by typing 'aldor -gloop' to the shell.
>
>      This will put you in an interactive compiler loop, at which you can
> type:
>
>      #include "aldor"
>      #include "aldorio"
>      stdout << 2+2 << newline
>      #quit
>
> These commands do not work for me. Clearly there is an
>
>      import from Integer
>
> missing here otherwise one gets the error
>
> [L8 C11] #1 (Error) No meaning for integer-style literal `2'.
>
> Ralf
>