Joined: 16 Jun 2003
Well, the ratio is far from such numbers. My estimation is that the code creation takes 2 times slower in ASM for small projects and close to 1 for big projects. But notice that the quality of the assembly language programs is much higher.
Joined: 24 Aug 2004
Location: (514107) 2015 BZ509
Repeat this 10 times: Assembly code is not C code.
After one understands that then everything else goes smoothly.
Lets' see: If you want C code then perhaps you can write C code and use a C compiler. If you want assembly code then perhaps you can write assembly code and use an assembler. I don't see C coders trying to make their code look like assembly. So why should assembly coders try to make their code look like C?
idle wrote: i would, despite his odd behaviour sometimes, select ... abakis macro extension
Thanks. Anyone can use the macros in ABAKIS/<CPU>/LANGUAGE.INC.
revolution wrote: So why should assembly coders try to make their code look like C?
A long time ago, I evolved from a simple one-dimensional "assembler coder" into a "custom multi-machine code generator" and am using TinyCC now. Not FASM/G anymore. My definition of "assembler" is any language that translates directly to machine code, binary 1s and 0s.
Why create/use macro languages? To make programs fast and easily, for high-volume production, OS portability, easier syntaxes (see example below), for conversion to/from C/C++, for fun, recreation, experimentation, testing algorithms, creating small utilities and games, to access machine code, for knowledge of semantics, for the ability to use BOTH "HL features" in addition to pure assembler and to do things which you can't do with a HL compiler. Using C style macro syntaxes is NOT the same as using a C compiler which doesn't have the power of FASM/G.
None of my macros prevent from writing 100% assembler like FreshLib's HL macro language does. IMO, the HL macro language included with FASM - struct, proc, invoke, .if, .while - is old, outdated and should be upgraded.
Try writing this in C, it will be much longer. What could be easier than this?
; Easiest file I/O example
include'z.inc' textt(128), f='LOG.TXT',\ s='EXAMPLE TEXT DATA' n=s.$
createf; create file
writes, n; write to current file
close; close after create
readt, n; read to t
sayt; display text
close; close after open
executef; execute maximize
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum