Emacspeak discussion list

[Robert Melton <lists AT robertmelton.com>]

Haden--

I actually had it built that way initially.  My reasons for changing it to 
prebuilt are:

1. Easier multi-file organization
2. Fail at build-time not at run-time.  This is a big one for me, as it makes 
it a good pairing with 
    the python version, which fails at runtime. 
3. The compile time can take a bit which would really slow startup and 
possibly confuse. 
4. Not sure how to message missing swift / broken compile from inside emacs.
5. Follows Apples best practices to build it using the Swift project 
structure 

That said, I wonder if this is a why-not-both situation.  I could merge my 
structure into one
large file with the swift header, then you could be pre-compiled or ad-hoc 
compiled. 

> On Oct 24, 2023, at 11:38, Haden Pike (via emacspeak Mailing List) 
> <emacspeak AT emacspeak.net> wrote:
> 
> I don't have a Mac any more, but I think Swift could also be used as an 
> interpreter? So you would add
> 
> #!/usr/bin/env xcrun swift
> 
> to the top of the server, and the user just has to have the xcode command 
> line tools installed. Seems easier than building a binary.


-- 
Robert "robertmeta" Melton