flat assembler
Message board for the users of flat assembler.

Index > IDE Development > Wink 6.92.03 (vertical selection + compiling)

Goto page Previous  1, 2, 3 ... 8, 9, 10 ... 19, 20, 21  Next
Author
Thread Post new topic Reply to topic
Tomasz Grysztar



Joined: 16 Jun 2003
Posts: 7725
Location: Kraków, Poland
Tomasz Grysztar
In fasmw Esc closes the current file (and whole program only when it was the last file).
Post 08 Sep 2010, 21:26
View user's profile Send private message Visit poster's website Reply with quote
ouadji



Joined: 24 Dec 2008
Posts: 1081
Location: Belgium
ouadji

+ Esc key for Tomasz. Wink

_________________
I am not young enough to know everything (Oscar Wilde)- Image


Last edited by ouadji on 27 Jan 2011, 17:26; edited 1 time in total
Post 08 Sep 2010, 21:37
View user's profile Send private message Send e-mail Reply with quote
bitRAKE



Joined: 21 Jul 2003
Posts: 2915
Location: [RSP+8*5]
bitRAKE
Tomasz Grysztar wrote:
Though it highlights those macro words even for non-Windows program that don't use the Windows headers.
This is important to me as well because I don't use the standard includes for windows. Although I haven't seen any conflict yet.


Ideas in no specific order of importance:

Some FASM directives are context specific - the options to format, for example. Can these be supported in a context sensitive way? Should the "include" in "jMP iNclUDe" really be highlighted as a directive?

Some instructions are also used to calculate values and receive incorrect highlighting:
Code:
CLIENT: ; define client area
        .X      = 1 shl 10
        .Y      = .X    
...here SHL gets highlighted as an instruction when clearly it is like * or + in this context.

Data directives should be in a separate category, imho. My reasoning has always been to distinguish things which create output from those which alter internal state of the assembler. This includes: d*, r*, and possibly align. There are other directives which create output, but only in an indirect manner.

Sizable (bigger) compiler output window, or output to new document.

I hope I don't sound like too much of a WIMP when I say this, but I have been spoiled by highlighted code: I find it easier to read, and faster to browse. I would go as far as to say I can code longer with diverse code to look at - tired eyes are less likely to wander. Thank you for taking on the task of extending FASMW - it is a pleasure to use. Very Happy

_________________
¯\(°_o)/¯ unlicense.org


Last edited by bitRAKE on 09 Sep 2010, 02:34; edited 1 time in total
Post 09 Sep 2010, 02:21
View user's profile Send private message Visit poster's website Reply with quote
revolution
When all else fails, read the source


Joined: 24 Aug 2004
Posts: 17281
Location: In your JS exploiting you and your system
revolution
bitRAKE wrote:
Should the "include" in "jMP iNclUDe" really be highlighted as a directive?
Yes. Because it is impossible to have the label "iNclUDe"
Code:
jMP iNclUDe
iNclUDe: ;<--- error: invalid argument.    
Post 09 Sep 2010, 02:26
View user's profile Send private message Visit poster's website Reply with quote
bitRAKE



Joined: 21 Jul 2003
Posts: 2915
Location: [RSP+8*5]
bitRAKE
Very Happy It works fine for me:
Code:
iNclUDe fix _iNclUDe

jMP iNclUDe
iNclUDe:    
...I see, it is kind of like a warning to user.
Post 09 Sep 2010, 02:39
View user's profile Send private message Visit poster's website Reply with quote
revolution
When all else fails, read the source


Joined: 24 Aug 2004
Posts: 17281
Location: In your JS exploiting you and your system
revolution
bitRAKE wrote:
Very Happy It works fine for me:
Code:
iNclUDe fix _iNclUDe

jMP iNclUDe
iNclUDe:    
...I see, it is kind of like a warning to user.
Touché. Wink

And if your code really looks like that then you deserve all the false highlighting you get.
Post 09 Sep 2010, 02:56
View user's profile Send private message Visit poster's website Reply with quote
bitRAKE



Joined: 21 Jul 2003
Posts: 2915
Location: [RSP+8*5]
bitRAKE
I can easily see myself doing something like "PE64:" or "readable:" label. Luckily, FASM provides a specific compile time error in response to this kind of thing. Sometimes I don't even think when labeling.
Post 09 Sep 2010, 04:57
View user's profile Send private message Visit poster's website Reply with quote
ouadji



Joined: 24 Dec 2008
Posts: 1081
Location: Belgium
ouadji
Code:
jMP iNclUDe
iNclUDe:
    

revolution :
Because it is impossible to have the label "iNclUDe" : correct

bitRAKE :
it is kind of like a warning to user : correct

but, for example,
Code:
proc proC ;ok (not "proc proc")
endp

endP :
jmp endP ;ok
    

bitRAKE,
Code:
pe64 :        ;(pe64, Pe64, pE64)
readable : ;both are not allowed with Wink (like fasmw)
    

Quote:

Some instructions are also used to calculate values and receive incorrect highlighting:

Code:
CLIENT: ; define client area
.X = 1 shl 10
.Y = .X

very difficult here to put a different color for "shl",
because in this case it's becoming "syntax parsing"
and it takes a lot of computation time. (sorry for my english)
Difficult to make a "real compiler colorful". This would be possible,
but it would be impossible to have a result in a usable time.
(I was forced to make choices)

However, I think I got a good result ...
especially with the multilines comments, the backslash, the long lines.
try this, and play with it and the long lines ... Smile
(especially on the border of long lines)
Code:
jmp proc_1.local_proc_1
    nono1:  .loco:   nono2:/*


          hello !


           */ proc  \
                proc_1  \
                    var7 : dword
                nop
               .local_proc_1 :
                nop
               /* comment */ mov eax,[var7]
              endp
              jmp nono1.loco
   
    


_________________
I am not young enough to know everything (Oscar Wilde)- Image


Last edited by ouadji on 09 Sep 2010, 09:09; edited 3 times in total
Post 09 Sep 2010, 08:25
View user's profile Send private message Send e-mail Reply with quote
Tomasz Grysztar



Joined: 16 Jun 2003
Posts: 7725
Location: Kraków, Poland
Tomasz Grysztar
ouadji wrote:
Code:
pe64 :        ;(pe64, Pe64, pE64)
readable : ;both are not allowed with Wink (like fasmw)
    
In fasm it may get improved in future, as I already consider making all the formatter-specific symbols parsed only inside the formatter's directives (like "format", "section" or "data"), and hence they would no longer be disallowed as labels.
Post 09 Sep 2010, 08:59
View user's profile Send private message Visit poster's website Reply with quote
ouadji



Joined: 24 Dec 2008
Posts: 1081
Location: Belgium
ouadji

Wink will monitor, no problem

_________________
I am not young enough to know everything (Oscar Wilde)- Image
Post 09 Sep 2010, 09:07
View user's profile Send private message Send e-mail Reply with quote
Tomasz Grysztar



Joined: 16 Jun 2003
Posts: 7725
Location: Kraków, Poland
Tomasz Grysztar
In fact, I just did it. Smile
Post 09 Sep 2010, 09:36
View user's profile Send private message Visit poster's website Reply with quote
ouadji



Joined: 24 Dec 2008
Posts: 1081
Location: Belgium
ouadji

grrrrrrrr Evil or Very Mad .... Wink Wink

_________________
I am not young enough to know everything (Oscar Wilde)- Image
Post 09 Sep 2010, 09:42
View user's profile Send private message Send e-mail Reply with quote
Tomasz Grysztar



Joined: 16 Jun 2003
Posts: 7725
Location: Kraków, Poland
Tomasz Grysztar
Here comes the list of formatter keywords that are no longer disallowed as labels, because they are now recognized in specific context only:
Code:
binary
code
coff
console
discardable
dll
dynamic
efi
efiboot
efiruntime
elf
elf64
executable
export
fixups
gui
import
interpreter
linkinfo
linkremove
ms
ms64
mz
native
note
notpageable
pe
pe64
readable
resource
shareable
static
wdm
writable
writeable    

Note that "data" is still disallowed as label, because it is also the name of directive.

And the directives that create context where those formatter symbols are recognized are:
Code:
data
format
section
segment    
Note that this means you still cannot define segment name "code", even though you can create such label.
Also there are some special cases: the "public" directive allows "static" keyword before the label name (and this also means you cannon make the label named "static" public). And "at" or "align" operators in the "format" or "section" definitions are followed by the numerical expressions where formatter symbols are not expected.
Post 09 Sep 2010, 10:09
View user's profile Send private message Visit poster's website Reply with quote
ouadji



Joined: 24 Dec 2008
Posts: 1081
Location: Belgium
ouadji

Wink will follow this change. Cool

I just need to adapt the information in the database.

Thank you Tomasz.

_________________
I am not young enough to know everything (Oscar Wilde)- Image
Post 09 Sep 2010, 10:26
View user's profile Send private message Send e-mail Reply with quote
revolution
When all else fails, read the source


Joined: 24 Aug 2004
Posts: 17281
Location: In your JS exploiting you and your system
revolution
Tomasz Grysztar wrote:
In fact, I just did it. Smile
Oh. Looks like another forced update to fasmarm is needed.
Post 09 Sep 2010, 10:30
View user's profile Send private message Visit poster's website Reply with quote
Tomasz Grysztar



Joined: 16 Jun 2003
Posts: 7725
Location: Kraków, Poland
Tomasz Grysztar
revolution wrote:
Oh. Looks like another forced update to fasmarm is needed.
If you need any assistance, just ask.
Post 09 Sep 2010, 10:53
View user's profile Send private message Visit poster's website Reply with quote
edemko



Joined: 18 Jul 2009
Posts: 549
edemko
Tomasz, will you integrate wink features?
Post 09 Sep 2010, 11:11
View user's profile Send private message Reply with quote
Tomasz Grysztar



Joined: 16 Jun 2003
Posts: 7725
Location: Kraków, Poland
Tomasz Grysztar
Of course not. As I said earlier I treat it as an enchanced community-developed fork, just what the Fresh was.
Post 09 Sep 2010, 11:18
View user's profile Send private message Visit poster's website Reply with quote
edemko



Joined: 18 Jul 2009
Posts: 549
edemko
Do you think ouadji or someone else will claim money compensation?
Post 09 Sep 2010, 11:21
View user's profile Send private message Reply with quote
Tomasz Grysztar



Joined: 16 Jun 2003
Posts: 7725
Location: Kraków, Poland
Tomasz Grysztar
edemko wrote:
Do you think ouadji or someone else will claim money compensation?
They can do it if they want. fasm's license allows a commercial product to be created on its base; so you can create your own fasm version and sell it, if you find people willing to pay for it.
Post 09 Sep 2010, 11:24
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, 3 ... 8, 9, 10 ... 19, 20, 21  Next

< 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-2020, Tomasz Grysztar. Also on YouTube, Twitter.

Website powered by rwasa.