Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
Zach Beane
zacl
Commits
a8d41385
Commit
a8d41385
authored
Oct 18, 2018
by
Dave Cooper
Browse files
Fixed formatting in README.md.
parent
9757d874
Changes
1
Show whitespace changes
Inline
Side-by-side
README.md
View file @
a8d41385
...
...
@@ -48,12 +48,12 @@ AllegroServe](https://github.com/genworks/aserve/tree/zacl-compatible)
has its system name as
`zaserve`
. This
`zaserve`
system definition
includes a dependency on ZACL, so you can load it simply by invoking
`
(ql:quickload :zaserve)
`
(ql:quickload :zaserve)
Of course, if for some reason you only want the
`zacl`
system itself,
you can load that with
`
(ql:quickload :zacl)
`
(ql:quickload :zacl)
## Limitations
...
...
@@ -86,9 +86,11 @@ With that said, AllegroServe will always run best on its native
platform, which is
[
Allegro
CL
](
https://franz.com/products/allegro-common-lisp/
)
. So if you want
to run AllegroServe for mission-critical or performance-critical
applications, then you may want to consider investing
[
Allegro
CL
](
https://franz.com/products/allegro-common-lisp/
)
. This option also
comes with the benefit of the dedicated, world-class
[
support from
Franz Inc. engineers
](
https://franz.com
)
.
applications, and with a guarantee of a supported, trouble-free
experience, then you may want to consider investing
[
Allegro
CL
](
https://franz.com/products/allegro-common-lisp/
)
for your
AllegroServe needs. This option also comes with the benefit of
dedicated, world-class
[
support from Franz
Inc. engineers
](
https://franz.com
)
.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment