Rasm Z80 assembler

[roudoudou]

I've tried with:

Code Select Expand

.\rasm.exe "project.asm"With the same result.
Maybe I'm missing something ...

i guess there is some output in the console right? this may help

for example, something like

Code Select Expand

Pre-processing [minimal.sna]
Assembling
Write snapshot v3 file minimal.sna
WriteSNA bank  0,1,2,3 packed
Total 4 banks (64K)


[roudoudou]

oh, i got it, one special case missed with that E5 byte...

will make a proper test and fix it...

anyway that does not explain that zero byte file...

EDIT; just runned some defb #E5,#00,#E5,#E5,#00,#E5,#E5,#E5 then it crashed...

fix this tonight

[roudoudou]

sorry for this, should have done this Autotest before... (doing this all day long, what a shame!)

new release, bugfixing the bugfix ^_^ https://github.com/EdouardBERGE/rasm/releases/tag/v2.2.1

[isidoro]

sorry for this, should have done this Autotest before... (doing this all day long, what a shame!)

new release, bugfixing the bugfix ^_^ https://github.com/EdouardBERGE/rasm/releases/tag/v2.2.1

Now it's working fine , thanks!!

[roudoudou]

New release https://github.com/EdouardBERGE/rasm/releases/tag/v2.2.2

Introducing new directive HFE for HFE floppy authoring (commands will be enriched in the future)

Documentation draft about that directive with examples http://rasm.wikidot.com/directives:hfe-creator

[krusty_benediction]

Great
This is not clear in the documentation: HFE directive does not allow saving files on disc ? It is just for low level stuffs ?
On an ergonomic side, EDSK and HFE seem to have similar features named differently or working differently. If I'm wrong, it's perfect, but if I'm not wrong some harmonization would be probably useful.

[roudoudou]

HFE Close will save the HFE

Probably some harmonization in a higher level (for example saving sectors in a row from Rasm memory), it mazy evolve

note: HFE is supposed to be used for low level tricks (protections, trackload, FDC experimentations)

[krusty_benediction]

I wrongly wrote my question: when saving, I had in mind "Amsdos file saving", not saving the content of the hfe file
But ok; you answer anyway: it is for low level stuff

Then I could suggest the SAVE command to consider the DSK parameter as a synonym of DISC or HFE and use the filetype extension to really know if it is a dsk or hfe.
This will allow you ta save on dsk or hfe without having to change the current syntax.
This ill help to push out the dsk format in favor of hfe too

ps: as time flies, I really hate more and more the standard way to handle directives in most z80 assemblers, this is really not ergonomic

[roudoudou]

Will think about how we can mix syntax, thanks

[lightforce6128]

[...]
ps: as time flies, I really hate more and more the standard way to handle directives in most z80 assemblers, this is really not ergonomic

Although this is a bit off-topic for this thread, I'm really curious about this topic. In syntax and functionality there is a big gap between an (old 8-bit) assembler language where the programmer has to think many levels in advance to avoid several pitfalls, compared to a modern high level language that does its best to guess what the programmer means by something close to simplified pseudo-code.

What do you mean with the "standard way to handle directives"? And are there ideas for improvement?

Since 1986 I had the feeling that there must be something between Assembler and e.g. Logo. From functionality this would be C, but I do not like its syntax, and some design choices were also made to simplify the compiler.

[krusty_benediction]

[...]
ps: as time flies, I really hate more and more the standard way to handle directives in most z80 assemblers, this is really not ergonomic

Although this is a bit off-topic for this thread, I'm really curious about this topic. In syntax and functionality there is a big gap between an (old 8-bit) assembler language where the programmer has to think many levels in advance to avoid several pitfalls, compared to a modern high level language that does its best to guess what the programmer means by something close to simplified pseudo-code.

What do you mean with the "standard way to handle directives"? And are there ideas for improvement?

Since 1986 I had the feeling that there must be something between Assembler and e.g. Logo. From functionality this would be C, but I do not like its syntax, and some design choices were also made to simplify the compiler.

I've just created a new topic to not pollute rasm one https://www.cpcwiki.eu/forum/programming/some-thoughts-for-modern-assembler-in-amstrad-world/new/#new

[roudoudou]

minimal update

https://github.com/EdouardBERGE/rasm/releases/tag/v2.2.3

HFE not protected as default
and RAM configuration default for snapshots