FA-90064 / Bytecode virtual machines / Member archive

Method descriptors: empty object type name accepted · case 04

A parameter written as "L;" parses as a class with an empty name.

Member previewVariant 4 · 3 implementations · 9 checks per implementation

Case contract

Parse a method descriptor "(args)ret". Field types: B C D F I J S Z, L<binary name>; with a non-empty name, and up to 255 leading "[" dimensions. V is allowed only as a non-array return type. Local-slot count: one extra slot for "this" unless static; J and D take two slots unless they are array element types. Return {args (readable names, "[]" per dimension), slots, ret} or ["ClassFormatError", position].

Why this case matters

Frame sizes and argument placement in bytecode VMs are derived from descriptors.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
empty class name rejected	`{"args": ["int", "int", "int", "int", ""], "ret": "void", "slots": 6}`	`["ClassFormatError", 5]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.