Camilo

I personally like the way https://github.com/apple/swift-package-manager works Example https://raw.githubusercontent.com/vapor/leaf/main/Package.swift ```swift // swift-tools-version:5.2 import PackageDescription let package = Package( name: "leaf", platforms: [ .macOS(.v10_15) ], products: [ .library(name: "Leaf", targets: ["Leaf"]),...

IMHO I think wren-cli is fine as it is with libuv because it is a project that acts as an example _Wren_ embed. A new wren-cli like project made from...

I think another option would be like DOME where the wren to c string is included in the CLI tool (and have a small C binary helper too). So there...

Indeed. A small binary would be needed to interpret such build scripts. Dome solved by using that https://github.com/domeengine/dome/blob/main/src/util/embed.c And Wren lang have this small test.c https://github.com/wren-lang/wren/blob/main/test/main.c to execute tests. So...

Using wren_cli for building wren_cli? thats something interesting and could free wren_cli from python dependency

I though that was just including the wren 0.3 release executables and use them to build newer versions of wren. Since the build scripts do not use lots of apis...

There is an alternative way of building the cli. That is including a copy of `wren.inc` files that are not supposed to be modified. Only for compiling the tool with...

Yes but they can be easily be modified for testing the new versions. So is better to have a non modified ones in a cache that is not supposed to...

I think this is a conversation for another PR/Issue. This issue can be subdivided into 3 problems 1 - PR: Fix the newline bug 2 - PR: Fix circular dependency....

This can be achieved by using the new attributes https://wren.io/classes.html#attributes and then the REPL could fetch them and show them 👍