non-inline text in parrot assembly?

[Tupshin Harper]

Parrot assembly supports inline strings, but are there any plans to have
it support a distinct .string (or similar) asm section? The main benefit
would be easier compatibility/portability with existing assembly code
generators. Is anybody aware of an existing assembly format that doesn't
support a separate string section?

-Tupshin

[Leopold Toetsch]

Tupshin Harper wrote:

You can use the .constant (PASM) or .const (IMCC) syntax, to keep
strings visually together.

> -Tupshin

leo

[Tupshin Harper]

Leopold Toetsch wrote:

> You can use the .constant (PASM) or .const (IMCC) syntax, to keep
> strings visually together.
>
>

> leo
>
Thanks. Apparently I'm being daft. I don't see any mention of pasm
sections(constant or otherwise) in the pod docs, nor do any of the
examples appear to use a constants section. What am I missing?

-Tupshin

[Leopold Toetsch]

Tupshin Harper wrote:

> Leopold Toetsch wrote:
>
>> You can use the .constant (PASM) or .const (IMCC) syntax, to keep
>> strings visually together.

> Thanks. Apparently I'm being daft. I don't see any mention of pasm
> sections(constant or otherwise) in the pod docs, nor do any of the
> examples appear to use a constants section. What am I missing?

Sorry nothing.
There are only IIRC 3 tests in parrot and 3 in imcc using these features.

$ perldoc assemble.pl
$ perldoc languages/imcc/docs/syntax.pod
$ perldoc languages/imcc/docs/macros.pod

But they are not very well covered in the main docs.

Additionally, string (and key and float constants) are a distinct
section in PBC, only the assembler doesn't care - or OTOH there is now
syntax to reference a string constant directly. This is all done via the
constant tabke.

> -Tupshin

leo

[gre...@focusresearch.com]

Tupshin --

Parrot Byte Code (.pbc) files (aka packfiles) have multiple sections, but
Parrot
Assembly (.pasm) files do not reference them explicitly. Literal constants
are
*implicitly* placed in the constant section of the .pbc file upon
assembly. The
.constant or .const directives allow you to name your constants, but the
net
result is equivalent.

Regards,

-- Gregor

Tupshin Harper <tup...@tupshin.com>
02/22/2003 02:31 PM

To: Leopold Toetsch <l...@toetsch.at>
cc: perl6-i...@perl.org
Subject: Re: non-inline text in parrot assembly?

Leopold Toetsch wrote:

> You can use the .constant (PASM) or .const (IMCC) syntax, to keep
> strings visually together.
>
>

> leo

>
Thanks. Apparently I'm being daft. I don't see any mention of pasm
sections(constant or otherwise) in the pod docs, nor do any of the
examples appear to use a constants section. What am I missing?

-Tupshin

[Tupshin Harper]

Leopold Toetsch wrote:

> Tupshin Harper wrote:
>
>> Thanks. Apparently I'm being daft. I don't see any mention of pasm
>> sections(constant or otherwise) in the pod docs, nor do any of the
>> examples appear to use a constants section. What am I missing?
>
> Sorry nothing.
> There are only IIRC 3 tests in parrot and 3 in imcc using these features.
>
> $ perldoc assemble.pl

Actually you're wrong ;-)
I was missing something, and that of course was "perldoc assemble.pl". ;-)
Thanks for the pointer, that contains a *lot* of information that
doesn't appear to be anywhere else(.constant, for example, is never
mentioned in docs/*.pod).

> But they are not very well covered in the main docs.

I would vote to move virtually all of this information out of
assemble.pl and into docs/parrot_assembly.pod (or something similar),
and have the perldoc for assemble.pl just be an overview + usage
information.

Thanks.

-Tupshin