[Ecls-list] compile-file-pathname bug

Juan Jose Garcia-Ripoll juanjose.garciaripoll at googlemail.com
Sat May 16 21:43:33 UTC 2009

On Sat, May 16, 2009 at 11:15 PM, Gabriel Dos Reis <gdr at cs.tamu.edu> wrote:
> | That has caused a lot of problems in the past, specially in Windows,
> | with really annoying messages popping up all the time about files
> | being corrupt: following what you say, the loading of binary files has
> | to be tried first, and sometimes the files are lisp sources, not
>  * otherwise, commit to loading a FASL.  A native dynamically loadable
>    module, (either EFL, PE, or MACH) has a magic numnber.  If that
>    magic number isn't present in the ultimate native module, then error
> Is that something you can agree to?

Please understand that I am not just being stubborn. I know about
magic files, but I did not have the knowledge nor the time to
implement them and found the current approach sufficient -- sincerely,
what is gained by forcing your own extension on compiled files that
can not be done by using temporary directories or real temporary names
(mkstemp)? -- But I am not opposing to this change. I do not find I
can do it right now myself

> Yes, but then even if the file had the 'right' extension (as the current
> situation in ECL), that in itself does not necessarily mean that the
> content is right.  So, one gets the same problem.

Well, the point is that right now we are not trying with every file
the binary approach. Hence no problems with errors.


Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28009 (Spain)

More information about the ecl-devel mailing list