erlang-luerl 1:1.0-2 source package in Ubuntu

Changelog

erlang-luerl (1:1.0-2) unstable; urgency=medium

  * Updated debian/watch

 -- Philipp Huebner <email address hidden>  Sat, 18 Dec 2021 11:26:28 +0100

Upload details

Uploaded by:
Ejabberd Packaging Team
Uploaded to:
Sid
Original maintainer:
Ejabberd Packaging Team
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Mantic release universe misc
Lunar release universe misc
Jammy release universe misc

Downloads

File Size SHA-256 Checksum
erlang-luerl_1.0-2.dsc 2.0 KiB f800820d25d3018bfe5e6030423453243a071a77c5340a58625e8262e0e20d7a
erlang-luerl_1.0.orig.tar.gz 121.6 KiB 636e720b0a490c67681ff2deaa4d3e0cdbeb2e59e259ac80732c7794874acdb4
erlang-luerl_1.0-2.debian.tar.xz 3.8 KiB 63dabbd3b65681d8d7faa50be32c6eebc9f309ac64cd5252d6f3641680f213ff

Available diffs

No changes file available.

Binary packages built by this source

erlang-luerl: implementation of Lua in Erlang

 An experimental implementation of Lua 5.2 written solely in pure Erlang
 .
 When to use Luerl:
 .
 Fast Language Switch: Luerl should allow you to switch between Erlang and Lua
 incredibly fast, introducing a way to use very small bits of logic programmed
 in Lua, inside an Erlang application, with good performance.
 .
 Multicore: Luerl provides a way to transparently utilize multicores. The
 underlying Erlang VM takes care of the distribution.
 .
 Microprocesses: It should give you a Lua environment that allows you to
 effortlessly run tens of thousands of Lua processes in parallel, leveraging
 the famed microprocesses implementation of the Erlang VM. The empty Luerl
 State footprint will be yet smaller than the C Lua State footprint.
 .
 Forking Up: Because of the immutable nature of the Luerl VM, it becomes a
 natural operation to use the same Lua State as a starting point for multiple
 parallel calculations.
 .
 However, Luerl will generally run slower than a reasonable native Lua
 implementation. This is mainly due the emulation of mutable data on top of an
 immutable world. There is really no way around this. An alternative would be
 to implement a special Lua memory outside of the normal Erlang, but this would
 defeat the purpose of Luerl. It would instead be then more logical to connect
 to a native Lua.
 .
 Some valid use cases for Luerl are:
  * Lua code will be run only occasionally and it wouldn't be worth managing
    an extra language implementation in the application;
  * the Lua code chunks are small so the slower speed is weighed up by Luerl's
    faster interface;
  * the Lua code calculates and reads variables more than changing them;
  * the same Lua State is repeatedly used to 'fork up' as a basis for
    massively many parallel calculations, based on the same state;
  * it is easy to run multiple instances of Luerl which could better utilise
    multicores.