On 10 July 2018 at 18:44, Ralf Hemmecke wrote:
> On 07/10/2018 06:35 PM, Waldek Hebisch wrote:
> > Just a comment: current Spad compiler essentially imports every
> > domain that is sees: types of function arguments, type of value,
> > etc. This is creasy, because set of visible functions
On 07/10/2018 06:35 PM, Waldek Hebisch wrote:
> Just a comment: current Spad compiler essentially imports every
> domain that is sees: types of function arguments, type of value,
> etc. This is creasy, because set of visible functions depends
> on exact computation path taken in the compiler --
[Replying privately as not totally thought through]
Proposal sounds like its ok, but does it deal with package imports,
especially for things like map and reduce operations?
To be a bit more specific my plan for aldor is to
1) introduce 'import from F', where F is a domain or package
Peter Broadbery wrote:
>
> A second issue is that Aldor is much stricter about imports and function
> declarations. I have a set of changes that may help to address these, but
> there is a bit more to do. If there's anyone who wants to help with these,
> it would be appreciated.
Just a
Just to add a little, I am working on addressing the compilation time
issue,
and the newer version is significantly faster, but there is more to be done.
A second issue is that Aldor is much stricter about imports and function
declarations. I have a set of changes that may help to address these,
Riccardo GUIDA wrote:
>
> Thoughts:
>
> * The Aldor compiler is an improved version of the Spad compiler, written by
> one of its authors. So, as a non-expert, I would blindly tend to say that
> Aldor compiler is "better" than Spad compiler. At least it has written
> documentation and, I
Dear Waldek
Could you comment on my (naive) thoughts & questions below?
I use quotes for admittedly-unprecise terms.
I'm pretty sure you've talked about this in the last decade, but the
information is quite spread around in the list.
Thoughts:
* The Aldor compiler is an improved version of
