Skip to content

Conversation

@headius
Copy link
Member

@headius headius commented Jan 22, 2026

Bit of cleanup and documentation here mostly.

  • prism.org already exists and we don't own it, so moved Maven groupID to org.jruby.
  • As this is a chicory-based binding for prism, renamed artifact to chicory-prism.
  • Added JRuby dependency, as the only current consumer of chicory-prism is JRuby and the parser will usually reference RubySymbol.
  • Moved make target java-wasm build output to java-wasm/src/main/resources.
  • Added a README with basic instructions for bootstrapping and building the artifact.

Nodes need access to RubySymbol and support APIs at least.
* It is a resource used as source code (in wasm) that is compiled
  for the project artifact.
* Added to Rake CLOBBER
with:
name: prism.wasm
path: java-wasm/src/test/resources/prism.wasm
path: java-wasm/src/main/resources/prism.wasm

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The prism.wasm file was very intentionally placed in test so that it doesn't get included in the resulting jar (it's redundant).

The Chicory compiler already generates a org/prism/PrismParser.meta file that is smaller and contains everything needed for execution.

instance = Instance.builder(module)
.withMemoryFactory(limits -> new ByteArrayMemory(new MemoryLimits(10, MemoryLimits.MAX_PAGES)))
.withMachineFactory(PrismModule::create)
.withMachineFactory(parser.machineFactory())

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: .withMachineFactory(PrismParser::create)

@@ -1,11 +1,12 @@
package org.prism;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a big deal, but you might want to align the package name to the new groupId.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants