Home  >  Article  >  Backend Development  >  harlock v.eleased

harlock v.eleased

WBOY
WBOYOriginal
2024-07-16 18:06:00577browse

harlock v.eleased

It is with immense pleasure that I announce that version 0.5.1 off the harlock scripting language is out!

Here is the detailed release log, with a list the artifacts to install the language on debian-like systems, or directly a binary for the supported architectures.

Release note + artifacts @github/Abathargh/harlock

Build from source

Notice that you can always compile and install harlock by executing:

go install github.com/Abathargh/harlock/cmd/harlock

or:

git clone https://github.com/Abathargh/harlock
make install

Release details

This v0.5.1 release is a bugfix one, that solidifies harlock usage within build pipelines.

The main issues that were tackled are:

  • Correctly handling runtime and evaluation errors being raised at the top-level scope to trigger a non-zero error code. This led to silent errors being passed inside of pipelines using harlock.
  • Drop support for go 1.15+ unsupported targets.
  • Adding previously missing .exe suffix for windows executable names when cross-compiling for windows on non-windows
  • Minor fixes to .gitignore and Makefile.

Last couple of releases included a new error system which was thoroughly tested and fixing it is the main reason for v0.5.1.

Usage and new developments

I've been using harlock a lot to test the avr_io nim library that I work on, alongside personal projects where I need firmware to be updated over the wire/air with huge success.

A nice working project using the language can be found in the bootloader example for avr_io, where it is used to showcase the library capabilities when writing bootloaders for embedded applications.

I wrote an in-depth article on how to use harlock for these kind of scenarios on antima at the following link.

The above is the detailed content of harlock v.eleased. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn