[Aldor-l] Questions

[ldragan at aldor.org]

Quoting Ralf Hemmecke <ralf at hemmecke.de>:

> So? That should be considered a bug, right? (And it is even terribly
> easy to fix by replacing in sal_string.as the line
>
> 	string(l:Literal):% == string(l pretend Pointer);
>
> by
>
> 	string(l:Literal):% == copy string(l pretend Pointer);
>
> .)

Yes, this is the solution I was thinking about, but this has to be  
done for all implementations of string function (aldor, axllib,  
algebra?). The other solution is to clearly explain in the User's  
Guide this behavior. Of course, there is another solution to modify  
the compiler to add a strcpy to all string literals.

I'm not sure this can be considered as a bug (it might be a feature  
;-) ). The manual does not specify that the user should be allowed to  
write string literals. The same is true for C: literals are not  
writable, and this is not a bug in the C compiler.

>
> But there are more than 1200 old bugs missing from the bugtracker, so
> why not also this one here...

They are in a different format and need to be included in the new bug  
tracking system.

--
Laurentiu