init file obligatory?
CoCoAInterpreter requires that there be a file
init.cocoa5 in the same directory as the packages.
If the file not found, the interpreter prints an error message (before the banner) and proceeds.
Is this the right behaviour?
#2 Updated by John Abbott over 1 year ago
I found this while trying to create a "quick start" CoCoA-5 by giving it an empty directory as the place to look for packages.
CoCoAInterpreter produced the following error message:
EmptyDir/init.cocoa5: No such file or directory
At least a "nicer" warning message should be printed. Perhaps something like this:
WARNING: missing or unreadable initialization file init.cocoa5
Not sure if the file name should be just the basename (i.e. without any directories),
the name as it appears currently (e.g.
EmptyDir/init.cocoa5above), or the full path.
Perhaps the current approach is a good compromise between readability for non-specialists
and helpfulness to hapless debuggers.
#6 Updated by Anna Maria Bigatti over 1 year ago
- % Done changed from 0 to 10
When I added
init.cocoa5 I did not consider the possibility of calling cocoa passing explicitely an empty directory instead of
Now we know it makes sense (very fast start of cocoa for calling builtin functions only).
So it should not give an error.
Should we instead (or as well) have a flag