flat assembler
Message board for the users of flat assembler.

Index > Compiler Internals > Fasm Multilangage Encoding

Goto page Previous  1, 2
Thread Post new topic Reply to topic

Joined: 04 Mar 2008
Posts: 563
Location: Germany
hopcode 24 Mar 2010, 02:10
revolution wrote:
...fasm be a unicode (or UTF-16) based assembler? ...

Yes, code-points, what else. It corresponds to this 4-days-words-thread, but
Tomasz Grysztar wrote:
The Challenger operates on 32-bit codepoints, not ASCII.

after Tomasz's fantasy had explicitly refunctionalized ( Wink and that is a good sign)
the ISO concept of codepoints i meant, there's no need to seek for explanation for at least a couple of days. Very Happy
revolution wrote:
...will have to say which version of notepad

you are a Sexy-Girl in my imagination.
anyway, very few UltraIde-S or Notescratch-Es will represent -by glyphs-
codepoints and bidi infos correctly without using a clever/complex algo/work.
Besides, programs cannot compile mixed code as in the picture
(arab code+english code) without a rule, a standard that doent rely
obviously on the visualization.

The matter is that apparently (or actually) there is no need to implement
in fasm the basic feature of eating UTF-16 codepoints au lieu de 8bit chars.
revolution wrote:
What was the purpose of the mixed ASCII/Arabic

1) you read it ?
yes ? ok, this is 50% the purpose.
2) would you like to compile that code with fasm as you see/read/modify it ?
Yes ? but there's no need to do it! yes again ?
also, a standard is required.

Cheers, Very Happy

btw: this sample code useful, cum grano salis
mov eax,1

instead of
mov eax,-1

...because imho negative returning to the caller is not the best
disposition to bring a new way of thinking nearer.

Post 24 Mar 2010, 02:10
View user's profile Send private message Visit poster's website Reply with quote
When all else fails, read the source

Joined: 24 Aug 2004
Posts: 20056
Location: In your JS exploiting you and your system
revolution 24 Mar 2010, 02:23
hopcode: I still don't get what you are suggesting. Your responses are vague and unclear.

Do you want your new version of fasm to be able to compile the ASCII/Arabic example?

Why have two copies of the same code?

What if the two copies are inconsistent with each other?

Who can be bothered to write two versions of everything anyway?

Why do you suddenly mention about negative/positive return values? What has the '-1' return value got to do with UTF-16 encoded files?
Post 24 Mar 2010, 02:23
View user's profile Send private message Visit poster's website Reply with quote
Display posts from previous:
Post new topic Reply to topic

Jump to:  
Goto page Previous  1, 2

< Last Thread | Next Thread >
Forum Rules:
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

Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.

Website powered by rwasa.