Hello, Oswald!
OB> oh, sure it "works". with my variable ah in gas being highlighted, etc.
OB> just as useful as "new" and "class", etc. all over my c sources.
That's bad style :) Write hundred times "Do not name variables as registers
names".
The same as in linux 2.4.x kernels was numerous va
On Thu, Mar 17, 2005 at 07:29:27AM +0200, Mike V. Gorchak wrote:
> It's works fine for me with GAS, NASM and TASM.
>
oh, sure it "works". with my variable ah in gas being highlighted, etc.
just as useful as "new" and "class", etc. all over my c sources.
> And how you planning to split NASM sources
Hello, Oswald!
OB> On Wed, Mar 16, 2005 at 07:45:45AM +0200, Mike V. Gorchak wrote:
??>> because assembler keywords different in the each product (WASM, MASM,
??>> TASM, GAS, NASM, etc) and I have tryied to add as much as possible
??>> keywords,
OB> i'm strictly against putting all the asm sy
On Wed, Mar 16, 2005 at 07:45:45AM +0200, Mike V. Gorchak wrote:
> because assembler keywords different in the each product (WASM, MASM,
> TASM, GAS, NASM, etc) and I have tryied to add as much as possible
> keywords,
>
i'm strictly against putting all the asm syntaxes in one file. it is
annoying e
Hello all !
I've did x86 assembler syntax file for highlighting (I
can't believe that I'm first who did it :-| ) and POVRay syntax highlight. Both
syntax files are complete near 80%, because assembler keywords different in the
each product (WASM, MASM, TASM, GAS, NASM, etc) and I have tryie
