mirror of
https://github.com/kanaka/mal.git
synced 2024-11-13 01:43:50 +03:00
8a19f60386
- Reorder README to have implementation list after "learning tool" bullet. - This also moves tests/ and libs/ into impls. It would be preferrable to have these directories at the top level. However, this causes difficulties with the wasm implementations which need pre-open directories and have trouble with paths starting with "../../". So in lieu of that, symlink those directories to the top-level. - Move the run_argv_test.sh script into the tests directory for general hygiene.
19 lines
1.0 KiB
Swift
19 lines
1.0 KiB
Swift
//******************************************************************************
|
||
// MAL - main
|
||
//******************************************************************************
|
||
|
||
// Swift requires that main() be invoked from a file named "main.swift". See the
|
||
// paragraph "Application Entry Points and “main.swift” on
|
||
// https://developer.apple.com/swift/blog/?id=7:
|
||
//
|
||
// You’ll notice that earlier we said top-level code isn’t allowed in most
|
||
// of your app’s source files. The exception is a special file named
|
||
// “main.swift”, which behaves much like a playground file, but is built
|
||
// with your app’s source code. The “main.swift” file can contain top-level
|
||
// code, and the order-dependent rules apply as well. In effect, the first
|
||
// line of code to run in “main.swift” is implicitly defined as the main
|
||
// entrypoint for the program. This allows the minimal Swift program to be
|
||
// a single line — as long as that line is in “main.swift”.
|
||
|
||
main()
|