Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #171171 > unrolled thread

how many lines you coded?

Started byfir <profesor.fir@gmail.com>
First post2023-07-23 10:29 -0700
Last post2023-08-01 10:17 -0700
Articles 20 on this page of 76 — 18 participants

Back to article view | Back to comp.lang.c


Contents

  how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-23 10:29 -0700
    Re: how many lines you coded? Bart <bc@freeuk.com> - 2023-07-23 18:44 +0100
      Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-23 11:12 -0700
    Re: how many lines you coded? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-23 20:32 +0200
      Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-23 11:51 -0700
        Re: how many lines you coded? Bonita Montero <Bonita.Montero@gmail.com> - 2023-07-23 21:18 +0200
          Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 05:10 -0700
            Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 05:19 -0700
              Re: how many lines you coded? Richard Harnden <richard.nospam@gmail.com> - 2023-07-24 13:45 +0100
                Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 05:51 -0700
                  Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 06:44 -0700
                    Re: how many lines you coded? Richard Harnden <richard.nospam@gmail.com> - 2023-07-24 15:36 +0100
                      Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 07:40 -0700
                  Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 07:29 -0700
                    Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 07:39 -0700
                    Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-25 02:34 -0700
      Re: how many lines you coded? Vir Campestris <vir.campestris@invalid.invalid> - 2023-07-23 20:48 +0100
        Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-23 13:29 -0700
        Re: how many lines you coded? David Brown <david.brown@hesbynett.no> - 2023-07-24 09:02 +0200
          Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 00:27 -0700
            Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 00:35 -0700
              Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 00:45 -0700
                Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 01:18 -0700
                  Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 01:19 -0700
          Re: how many lines you coded? Bart <bc@freeuk.com> - 2023-07-24 11:21 +0100
            Re: how many lines you coded? David Brown <david.brown@hesbynett.no> - 2023-07-24 20:01 +0200
              Re: how many lines you coded? scott@slp53.sl.home (Scott Lurndal) - 2023-07-24 18:20 +0000
                Re: how many lines you coded? Bart <bc@freeuk.com> - 2023-07-24 20:49 +0100
                  Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 13:13 -0700
                    Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-24 13:22 -0700
            Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-25 08:51 -0700
              Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-25 09:16 -0700
              Re: how many lines you coded? Bart <bc@freeuk.com> - 2023-07-25 18:48 +0100
                Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-25 11:13 -0700
                  Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-25 11:26 -0700
                    Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-25 11:34 -0700
                      Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-25 11:46 -0700
                        Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-25 12:02 -0700
                  Re: how many lines you coded? Bart <bc@freeuk.com> - 2023-07-25 22:14 +0100
                    Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-25 14:35 -0700
                      Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-25 15:31 -0700
    Re: how many lines you coded? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-23 12:42 -0700
      Re: how many lines you coded? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-25 20:36 -0700
        Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-26 01:44 -0700
    Re: how many lines you coded? John McCue <jmccue@fuzzball.jmcunx.com> - 2023-07-25 20:26 +0000
      Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-25 14:52 -0700
    Re: how many lines you coded? Ed Prochak <edprochak@gmail.com> - 2023-07-26 08:04 -0700
      Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-27 01:16 -0700
        Re: how many lines you coded? Ed Prochak <edprochak@gmail.com> - 2023-07-30 21:38 -0700
    Re: how many lines you coded? Lynn McGuire <lynnmcguire5@gmail.com> - 2023-07-28 19:53 -0500
      Re: how many lines you coded? Ed Prochak <edprochak@gmail.com> - 2023-07-30 21:40 -0700
        Re: how many lines you coded? scott@slp53.sl.home (Scott Lurndal) - 2023-07-31 14:54 +0000
          Re: how many lines you coded? Lynn McGuire <lynnmcguire5@gmail.com> - 2023-07-31 23:22 -0500
    Re: how many lines you coded? aph@littlepinkcloud.invalid - 2023-07-31 09:29 +0000
      Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-31 05:10 -0700
        Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-31 05:16 -0700
          Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-31 05:36 -0700
            Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-31 07:00 -0700
        Re: how many lines you coded? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-31 05:27 -0700
          Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-31 05:41 -0700
            Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-31 05:51 -0700
              Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-07-31 05:59 -0700
          Re: how many lines you coded? aph@littlepinkcloud.invalid - 2023-08-04 17:57 +0000
            Re: how many lines you coded? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-04 11:05 -0700
              Re: how many lines you coded? scott@slp53.sl.home (Scott Lurndal) - 2023-08-04 19:03 +0000
                Re: how many lines you coded? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-04 12:24 -0700
                  Re: how many lines you coded? gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-04 19:27 +0000
                Was Dijkstra a "lefty" ? (Was: how many lines you coded?) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-04 19:26 +0000
                  Re: Was Dijkstra a "lefty" ? (Was: how many lines you coded?) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-04 13:54 -0700
                Re: how many lines you coded? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-08-04 19:47 -0700
                  Again, OT is OT! (Was: how many lines you coded?) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-05 03:51 +0000
                  Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-08-05 03:39 -0700
              [OT, Sorry] Re: how many lines you coded? aph@littlepinkcloud.invalid - 2023-08-05 03:02 +0000
            Re: how many lines you coded? Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-04 19:41 +0000
    Re: how many lines you coded? jak <nospam@please.ty> - 2023-08-01 18:09 +0200
      Re: how many lines you coded? fir <profesor.fir@gmail.com> - 2023-08-01 10:17 -0700

Page 1 of 4  [1] 2 3 4  Next page →


#171171 — how many lines you coded?

Fromfir <profesor.fir@gmail.com>
Date2023-07-23 10:29 -0700
Subjecthow many lines you coded?
Message-ID<dbb29689-380e-4d7c-8088-91d68e418033n@googlegroups.com>
how many lines you coded in your life? if you give an answer try to be real 
(and not count data and duplicates)
i myself estimated 200-300k hovever after thinking i think it may be closer to 200k (my newer projects take about 130k or something more but i also got some older i coand count now.. i would say for sure it was no less than 170k but how many above this thios one i can count/memorize now)

are you able to estimate?

[toc] | [next] | [standalone]


#171172

FromBart <bc@freeuk.com>
Date2023-07-23 18:44 +0100
Message-ID<u9joua$acau$1@dont-email.me>
In reply to#171171
On 23/07/2023 18:29, fir wrote:
> how many lines you coded in your life? if you give an answer try to be real
> (and not count data and duplicates)
> i myself estimated 200-300k hovever after thinking i think it may be closer to 200k (my newer projects take about 130k or something more but i also got some older i coand count now.. i would say for sure it was no less than 170k but how many above this thios one i can count/memorize now)
> 
> are you able to estimate?

A million lines? I've no idea. But a lot of it wouldn't be fresh code, 
but overhauling some existing project.

But I also started longer ago. Some early programs would have been 100% 
assembly code, which have a bigger line count.

All currently active projects are about 200Kloc counting latest 
versions, across all languages.

[toc] | [prev] | [next] | [standalone]


#171174

Fromfir <profesor.fir@gmail.com>
Date2023-07-23 11:12 -0700
Message-ID<4c2cc02a-f0c2-4949-9132-ffd9054839c1n@googlegroups.com>
In reply to#171172
niedziela, 23 lipca 2023 o 19:44:56 UTC+2 Bart napisał(a):
> On 23/07/2023 18:29, fir wrote: 
> > how many lines you coded in your life? if you give an answer try to be real 
> > (and not count data and duplicates) 
> > i myself estimated 200-300k hovever after thinking i think it may be closer to 200k (my newer projects take about 130k or something more but i also got some older i coand count now.. i would say for sure it was no less than 170k but how many above this thios one i can count/memorize now) 
> > 
> > are you able to estimate?
> A million lines? I've no idea. But a lot of it wouldn't be fresh code, 
> but overhauling some existing project. 
> 
> But I also started longer ago. Some early programs would have been 100% 
> assembly code, which have a bigger line count. 
> 
> All currently active projects are about 200Kloc counting latest 
> versions, across all languages.

you shouldnt count duplicates.. i guess programers who code long and often are about milion and maybe more...btw i checked my folder and copied all c files in one folder it showed 6 MB of .c filess all mine and no data - there may be some percent of duplicates of oleder and more new versions of some files i attached but still there are not all code only the more new  yhen it convince me my estimation was right something between 200k and 300k - all c and 2k lines of python , few lines of assembly and javascript (code itself is not specially interesting so the world would not lost to much if it would get lost etc, though i wopuld be pity - but some ideas (the one i often talked are interesting).. i know i probably should finish my compiler furia but thats damn consumption of time.. but probbaly will need to do that but not yet now

[toc] | [prev] | [next] | [standalone]


#171176

FromBonita Montero <Bonita.Montero@gmail.com>
Date2023-07-23 20:32 +0200
Message-ID<u9jro5$an58$1@dont-email.me>
In reply to#171171
Am 23.07.2023 um 19:29 schrieb fir:
> how many lines you coded in your life? if you give an answer try to be real
> (and not count data and duplicates)
> i myself estimated 200-300k hovever after thinking i think it may be closer to 200k (my newer projects take about 130k or something more but i also got some older i coand count now.. i would say for sure it was no less than 170k but how many above this thios one i can count/memorize now)

For sure in assembly, because that's easier to learn than C. ;-)

[toc] | [prev] | [next] | [standalone]


#171177

Fromfir <profesor.fir@gmail.com>
Date2023-07-23 11:51 -0700
Message-ID<defddd75-8dae-4ec6-b5fe-0e81a9c8f3fdn@googlegroups.com>
In reply to#171176
niedziela, 23 lipca 2023 o 20:32:50 UTC+2 Bonita Montero napisał(a):
> Am 23.07.2023 um 19:29 schrieb fir: 
> > how many lines you coded in your life? if you give an answer try to be real 
> > (and not count data and duplicates) 
> > i myself estimated 200-300k hovever after thinking i think it may be closer to 200k (my newer projects take about 130k or something more but i also got some older i coand count now.. i would say for sure it was no less than 170k but how many above this thios one i can count/memorize now)
> For sure in assembly, because that's easier to learn than C. ;-)

i dont get the joke at all..btw it seems that to resolve such problemst there is need of some file manager for code, something like total commander program but where you got only code files and its relatives..something like code 'treasury'/or 'code vault' (but in a form resembling total commander)

[toc] | [prev] | [next] | [standalone]


#171178

FromBonita Montero <Bonita.Montero@gmail.com>
Date2023-07-23 21:18 +0200
Message-ID<u9jues$avqo$1@dont-email.me>
In reply to#171177
Am 23.07.2023 um 20:51 schrieb fir:
> niedziela, 23 lipca 2023 o 20:32:50 UTC+2 Bonita Montero napisał(a):
>> Am 23.07.2023 um 19:29 schrieb fir:
>>> how many lines you coded in your life? if you give an answer try to be real
>>> (and not count data and duplicates)
>>> i myself estimated 200-300k hovever after thinking i think it may be closer to 200k (my newer projects take about 130k or something more but i also got some older i coand count now.. i would say for sure it was no less than 170k but how many above this thios one i can count/memorize now)
>> For sure in assembly, because that's easier to learn than C. ;-)
> 
> i dont get the joke at all..

You missed the joke.
It's the same distance with C and C++. Assembly is even more easier
to learn, but writing real softwar is much harder. The relationship
keeps the same with C and C++ but at a higher level for both languages.

[toc] | [prev] | [next] | [standalone]


#171203

Fromfir <profesor.fir@gmail.com>
Date2023-07-24 05:10 -0700
Message-ID<42232ebf-a9bb-4921-8903-04dd327a7613n@googlegroups.com>
In reply to#171178
niedziela, 23 lipca 2023 o 21:19:06 UTC+2 Bonita Montero napisał(a):
> Am 23.07.2023 um 20:51 schrieb fir: 
> > niedziela, 23 lipca 2023 o 20:32:50 UTC+2 Bonita Montero napisał(a): 
> >> Am 23.07.2023 um 19:29 schrieb fir: 
> >>> how many lines you coded in your life? if you give an answer try to be real 
> >>> (and not count data and duplicates) 
> >>> i myself estimated 200-300k hovever after thinking i think it may be closer to 200k (my newer projects take about 130k or something more but i also got some older i coand count now.. i would say for sure it was no less than 170k but how many above this thios one i can count/memorize now) 
> >> For sure in assembly, because that's easier to learn than C. ;-) 
> > 
> > i dont get the joke at all..
> You missed the joke. 
> It's the same distance with C and C++. Assembly is even more easier 
> to learn, but writing real softwar is much harder. The relationship 
> keeps the same with C and C++ but at a higher level for both languages.

i wrote my own assembler (org-asm) you my check it

https://fastupload.io/CYnB7m6CLilssjs/file

it compiles 3 examples...the attached dll is to run second example and thsi ddl is for opening window which my exampel ina ssembly calls to draw mandelbrot set 

hovever the resulted exe is simple and has no exception section which may be reason windows defender or other programs can false identify it as malvare it is strictly what you code in asm only

[toc] | [prev] | [next] | [standalone]


#171204

Fromfir <profesor.fir@gmail.com>
Date2023-07-24 05:19 -0700
Message-ID<0cd3648c-3119-4db6-abab-ae381fa18babn@googlegroups.com>
In reply to#171203
poniedziałek, 24 lipca 2023 o 14:10:54 UTC+2 fir napisał(a):
> i wrote my own assembler (org-asm) you my check it 
> 
> https://fastupload.io/CYnB7m6CLilssjs/file 
> 
> it compiles 3 examples...the attached dll is to run second example and thsi ddl is for opening window which my exampel ina ssembly calls to draw mandelbrot set 
> 
> hovever the resulted exe is simple and has no exception section which may be reason windows defender or other programs can false identify it as malvare it is strictly what you code in asm only

you may se the nice output log from it


+----------------------------------------------------------------------------+
|                                                                            |
| Organic Assembler (org-asm) by fir, december of 2020    (;ast update V.22) |
|                                                                            |
| note: this is  early version with far from elaborate                       |
| error messages and not strictly all of the mnemonics implemented,          |
| hovever it does the work and i find it nice and usefull                    |
|                                                                            |
| right now it is able to assemble win32/x86 exe files (no output as dll     |
| yet) with any possible dll imports, so youre basicaly able to assemble     |
| any win32 app with it                                                      |
|                                                                            |
+----------------------------------------------------------------------------+
| example use: org-asm input.asm output.exe                                  |
|              org-asm program.asm program.exe -no_console                   |
|                                                                            |
+----------------------------------------------------------------------------+
| known problems and limits:                                                 |
|                                                                            |
| - use ansi/ascii text as input asm file (if its unicode please open it     |
|   with notepas and save as ansi)                                           |
| - syntax error reporting are at the moment almost non existant (i will     |
|   mend it)                                                                 |
| - there are some hardcoded limits as to numbers of dll to inport (now set  |
|   to 300) size of code and data sections of exe (ow set to few megabytes)  |
|   i will remove most of them                                               |
| - not strictly all mnemonics typed                                         |
| - one cant use some character in string literals (like ,/" use "\x2c \x2f  |
|   \x22" type codes instead (i will mend it)                                |
| - no dlls can be asembled yet                                              |
| - there are places when expected syntax may be a bit rigid, i will men it  |
|                                                                            |
+----------------------------------------------------------------------------+
------------------------------------------------------------------------------
 Opening: input2.asm
------------------------------------------------------------------------------
 Basic PE header settings:

  attached console window is set off
------------------------------------------------------------------------------
 Code selected for assembly : 

   0 (l.    2) jmp start
   1 (l.   42) count_mandelbrot_areafragment_coeficients:
   2 (l.   50) mov eax -2
   3 (l.   51) cvt si2ss x2 eax
   4 (l.   53) mov ss x1 (man.lx)
   5 (l.   54) div ss x1 x2
   6 (l.   55) add ss x1 (man.ox)
   7 (l.   56) mov ss (man.start.x) x1
   8 (l.   58) mov ss x1 (man.ly)
   9 (l.   59) div ss x1 x2
  10 (l.   60) add ss x1 (man.oy)
  11 (l.   61) mov ss (man.start.y) x1
  12 (l.   63) mov eax ("green.fire.dll"->frame_size_x)
  13 (l.   64) mov ebx (eax)
  14 (l.   65) cvt si2ss x2 ebx
  15 (l.   66) mov ss x1 (man.lx)
  16 (l.   67) div ss x1 x2
  17 (l.   68) mov ss (man.dx) x1
  18 (l.   70) mov eax ("green.fire.dll"->frame_size_y)
  19 (l.   71) mov ebx (eax)
  20 (l.   72) cvt si2ss x2 ebx
  21 (l.   73) mov ss x1 (man.ly)
  22 (l.   74) div ss x1 x2
  23 (l.   75) mov ss (man.dy) x1
  24 (l.   77) ret
  25 (l.   81) calc_mandelbtot_for_esi_edi:
  26 (l.   90) cvt si2ss x0 esi
  27 (l.   91) mov ss x1 (man.dx)
  28 (l.   92) mul ss x0 x1
  29 (l.   93) add ss x0 (man.start.x)
  30 (l.   94) mov ss (c.re) x0
  31 (l.   96) cvt si2ss x0 edi
  32 (l.   97) mov ss x1 (man.dy)
  33 (l.   98) mul ss x0 x1
  34 (l.   99) add ss x0 (man.start.y)
  35 (l.  100) mov ss (c.im) x0
  36 (l.  103) mov ecx 0
  37 (l.  104) mov ss x3 (c.re)
  38 (l.  105) mov ss x4 (c.im)
  39 (l.  106) mov ss x0 x3
  40 (l.  107) mov ss x1 x4
  41 (l.  108) mov ss x2 (four)
  42 (l.  109) mov ss x5 x0
  43 (l.  110) iterations:
  44 (l.  111) mov ss x6 x1
  45 (l.  112) mul ss x5 x5
  46 (l.  113) mul ss x6 x6
  47 (l.  114) mov ss x7 x5
  48 (l.  114) add ss x7 x6
  49 (l.  115) comi ss x7 x2
  50 (l.  115) jae out
  51 (l.  116) sub ss x5 x6
  52 (l.  116) add ss x5 x3
  53 (l.  117) mul ss  x1 x0
  54 (l.  117) add ss  x1 x1
  55 (l.  117) add ss  x1 x4
  56 (l.  118) mov ss  x0 x5
  57 (l.  119) inc ecx
  58 (l.  119) cmp ecx 256
  59 (l.  119) jl iterations
  60 (l.  120) mov ecx 0xff0000
  61 (l.  120) ret
  62 (l.  121) out:
  63 (l.  122) push eax
  64 (l.  123) mov eax ecx
  65 (l.  124) shl eax 8
  66 (l.  125) add eax ecx
  67 (l.  126) shl eax 8
  68 (l.  127) add eax ecx
  69 (l.  128) mov ecx eax
  70 (l.  129) pop eax
  71 (l.  129) ret
  72 (l.  164) print_eax:
  73 (l.  167) push eax
  74 (l.  168) push note_eax
  75 (l.  169) call (msvcrt.dll->printf)
  76 (l.  170) pop eax
  77 (l.  171) pop eax
  78 (l.  172) ret
  79 (l.  176) ProcessKeyDown:
  80 (l.  182) mov eax (esp+4)
  81 (l.  183) mov (last_key_pressed) eax
  82 (l.  184) mov eax (last_key_pressed)
  83 (l.  185) cmp eax (PAGE_UP)
  84 (l.  186) jne if_0_end
  85 (l.  187) call print_eax
  86 (l.  189) if_0_end:
  87 (l.  191) ret
  88 (l.  195) ProcessRMBDown:
  89 (l.  201) mov ss  x1 (man.lx)
  90 (l.  202) mov ss  x2 (man.zoom.out)
  91 (l.  203) mul ss  x1 x2
  92 (l.  204) mov ss  (man.lx) x1
  93 (l.  206) mov ss  x1 (man.ly)
  94 (l.  207) mov ss  x2 (man.zoom.out)
  95 (l.  208) mul ss  x1 x2
  96 (l.  209) mov ss  (man.ly) x1
  97 (l.  211) ret
  98 (l.  216) ProcessLMBDown:
  99 (l.  221) mov eax (esp+4)
 100 (l.  221) mov (mouse_down_x) eax
 101 (l.  222) call print_eax
 102 (l.  224) mov eax (esp+8)
 103 (l.  224) mov (mouse_down_y) eax
 104 (l.  225) call print_eax
 105 (l.  234) mov  eax (mouse_down_x)
 106 (l.  235) cvt si2ss x1 eax
 107 (l.  236) mov  eax ("green.fire.dll"->frame_size_x)
 108 (l.  237) mov  ebx (eax)
 109 (l.  239) cvt si2ss x2 ebx
 110 (l.  241) div ss x1 x2
 111 (l.  242) mul ss x1 (man.lx)
 112 (l.  243) add ss x1 (man.ox)
 113 (l.  245) mov ss x2 (man.lx)
 114 (l.  246) mov eax -2
 115 (l.  247) cvt si2ss x3 eax
 116 (l.  248) div ss x2 x3
 117 (l.  250) add ss x1 x2
 118 (l.  251) mov ss (man.ox) x1
 119 (l.  255) mov  eax (mouse_down_y)
 120 (l.  256) cvt si2ss x1 eax
 121 (l.  257) mov  eax (green.fire.dll->frame_size_y)
 122 (l.  258) mov  ebx (eax)
 123 (l.  260) cvt si2ss x2 ebx
 124 (l.  262) div ss x1 x2
 125 (l.  263) mul ss x1 (man.ly)
 126 (l.  264) add ss x1 (man.oy)
 127 (l.  266) mov ss x2 (man.ly)
 128 (l.  267) mov eax -2
 129 (l.  268) cvt si2ss x3 eax
 130 (l.  269) div ss x2 x3
 131 (l.  271) add ss x1 x2
 132 (l.  272) mov ss (man.oy) x1
 133 (l.  277) mov ss  x1 (man.lx)
 134 (l.  278) mov ss  x2 (man.zoom)
 135 (l.  279) div ss  x1 x2
 136 (l.  280) mov ss  (man.lx) x1
 137 (l.  282) mov ss  x1 (man.ly)
 138 (l.  283) mov ss  x2 (man.zoom)
 139 (l.  284) div ss  x1 x2
 140 (l.  285) mov ss  (man.ly) x1
 141 (l.  294) ret
 142 (l.  298) OnResize:
 143 (l.  298) ret
 144 (l.  301) ProcessMouseMove:
 145 (l.  301) ret
 146 (l.  305) RunFrame:
 147 (l.  307) push 0x007000
 148 (l.  307) call (green.fire.dll->ClearFrameData)
 149 (l.  307) pop eax
 150 (l.  309) call count_mandelbrot_areafragment_coeficients
 151 (l.  311) mov eax (green.fire.dll->frame_bitmap)
 152 (l.  311) mov ebp (eax)
 153 (l.  312) mov eax (green.fire.dll->frame_size_x)
 154 (l.  312) mov ebx (eax)
 155 (l.  313) mov eax (green.fire.dll->frame_size_y)
 156 (l.  313) mov edx (eax)
 157 (l.  315) mov edi 0
 158 (l.  316) loop_y:
 159 (l.  317) mov esi 0
 160 (l.  318) loop_x:
 161 (l.  319) push edx
 162 (l.  320) mov eax edi
 163 (l.  320) mul eax ebx
 164 (l.  320) add eax esi
 165 (l.  320) shl eax 2
 166 (l.  320) add eax ebp
 167 (l.  321) pop edx
 168 (l.  322) call calc_mandelbtot_for_esi_edi
 169 (l.  323) mov (eax) ecx
 170 (l.  324) inc esi
 171 (l.  324) cmp esi ebx
 172 (l.  324) jl loop_x
 173 (l.  325) inc edi
 174 (l.  325) cmp edi edx
 175 (l.  325) jl loop_y
 176 (l.  326) ret
 177 (l.  337) start:
 178 (l.  338) push ProcessMouseMove
 179 (l.  338) call (green.fire.dll->RegisterMouseMove)
 180 (l.  338) pop eax
 181 (l.  339) push ProcessLMBDown
 182 (l.  339) call (green.fire.dll->RegisterLeftMouseButtonDown)
 183 (l.  339) pop eax
 184 (l.  340) push ProcessRMBDown
 185 (l.  340) call (green.fire.dll->RegisterRightMouseButtonDown)
 186 (l.  340) pop eax
 187 (l.  342) push ProcessKeyDown
 188 (l.  342) call (green.fire.dll->RegisterKeyDown)
 189 (l.  342) pop eax
 190 (l.  344) push OnResize
 191 (l.  344) call (green.fire.dll->RegisterOnResize)
 192 (l.  344) pop eax
 193 (l.  345) push RunFrame
 194 (l.  345) call (green.fire.dll->RegisterRunFrame)
 195 (l.  345) pop eax
 196 (l.  347) push 10
 197 (l.  347) call (green.fire.dll->SetSleepValue)
 198 (l.  347) pop eax
 199 (l.  351) push 480
 200 (l.  351) push 640
 201 (l.  352) push 480
 202 (l.  352) push 640
 203 (l.  353) push 20
 204 (l.  353) push 20
 205 (l.  354) push title
 206 (l.  354) call (green.fire.dll->SetupWindow3)
 207 (l.  355) add esp 20
 208 (l.  357) mov eax 0
 209 (l.  358) ret
------------------------------------------------------------------------------
 Data selected for build : 

   0 (l.   29) man.ox:  -0.6
   1 (l.   30) man.oy:  0.0
   2 (l.   31) man.lx:  4.0
   3 (l.   32) man.ly:  3.0
   4 (l.   33) man.start.x:  -0.0
   5 (l.   34) man.start.y: -0.0
   6 (l.   35) man.dx:  -0.0
   7 (l.   36) man.dy:  -0.0
   8 (l.   85) c.re: 0.0
   9 (l.   86) c.im: 0.0
  10 (l.   87) four: 4.0
  11 (l.  165) note_eax: "\x0d\0x0a eax = %d \x00"
  12 (l.  178) last_key_pressed:   0i
  13 (l.  179) PAGE_UP:  33i
  14 (l.  197) man.zoom.out: 1.25
  15 (l.  218) mouse_down_x:   0i
  16 (l.  219) mouse_down_y:   0i
  17 (l.  275) man.zoom: 1.25
  18 (l.  349) title: "example assembler app \x00"
------------------------------------------------------------------------------
 bss selected for build : 

 (none) 
------------------------------------------------------------------------------

 Building imports :  

  912 (0x0390) bytes stored in import section 


  green.fire.dll
    frame_size_x  (0x00402354)
    frame_size_y  (0x00402358)
    ClearFrameData  (0x0040235c)
    frame_bitmap  (0x00402360)
    RegisterMouseMove  (0x00402364)
    RegisterLeftMouseButtonDown  (0x00402368)
    RegisterRightMouseButtonDown  (0x0040236c)
    RegisterKeyDown  (0x00402370)
    RegisterOnResize  (0x00402374)
    RegisterRunFrame  (0x00402378)
    SetSleepValue  (0x0040237c)
    SetupWindow3  (0x00402380)

  msvcrt.dll
    printf  (0x00402388)

------------------------------------------------------------------------------

 Building data section : 

  label  man.ox:  (0x00403000)  
  label  man.oy:  (0x00403004)  
  label  man.lx:  (0x00403008)  
  label  man.ly:  (0x0040300c)  
  label  man.start.x:  (0x00403010)  
  label  man.start.y:  (0x00403014)  
  label  man.dx:  (0x00403018)  
  label  man.dy:  (0x0040301c)  
  label  c.re:  (0x00403020)  
  label  c.im:  (0x00403024)  
  label  four:  (0x00403028)  
  label  note_eax:  (0x0040302c)  
  label  last_key_pressed:  (0x0040303d)  
  label  PAGE_UP:  (0x00403041)  
  label  man.zoom.out:  (0x00403045)  
  label  mouse_down_x:  (0x00403049)  
  label  mouse_down_y:  (0x0040304d)  
  label  man.zoom:  (0x00403051)  
  label  title:  (0x00403055)  

  108 (0x006c) bytes collected in data section 

  403000 9a 99 19 bf 00 00 00 00 00 00 80 40 00 00 40 40
  403010 00 00 00 80 00 00 00 80 00 00 00 80 00 00 00 80
  403020 00 00 00 00 00 00 00 00 00 00 80 40 0d 5c 30 78
  403030 30 61 20 65 61 78 20 3d 20 25 64 20 00 00 00 00
  403040 00 21 00 00 00 00 00 a0 3f 00 00 00 00 00 00 00
  403050 00 00 00 a0 3f 65 78 61 6d 70 6c 65 20 61 73 73
  403060 65 6d 62 6c 65 72 20 61 70 70 20 00
------------------------------------------------------------------------------

 Building bss section : 

  bss start:  (0x4000)   
  bss  size:  (0x0000) 

 stored bss labels: 

------------------------------------------------------------------------------

 Buiding code section: 

  Assembling asm : 

  885 (0x0375) bytes assembled: 
 
  401000 e9 ea 02 00 00 b8 fe ff ff ff f3 0f 2a d0 f3 0f
  401010 10 0d 08 30 40 00 f3 0f 5e ca f3 0f 58 0d 00 30
  401020 40 00 f3 0f 11 0d 10 30 40 00 f3 0f 10 0d 0c 30
  401030 40 00 f3 0f 5e ca f3 0f 58 0d 04 30 40 00 f3 0f
  401040 11 0d 14 30 40 00 a1 54 23 40 00 8b 18 f3 0f 2a
  401050 d3 f3 0f 10 0d 08 30 40 00 f3 0f 5e ca f3 0f 11
  401060 0d 18 30 40 00 a1 58 23 40 00 8b 18 f3 0f 2a d3
  401070 f3 0f 10 0d 0c 30 40 00 f3 0f 5e ca f3 0f 11 0d
  401080 1c 30 40 00 c3 f3 0f 2a c6 f3 0f 10 0d 18 30 40
  401090 00 f3 0f 59 c1 f3 0f 58 05 10 30 40 00 f3 0f 11
  4010a0 05 20 30 40 00 f3 0f 2a c7 f3 0f 10 0d 1c 30 40
  4010b0 00 f3 0f 59 c1 f3 0f 58 05 14 30 40 00 f3 0f 11
  4010c0 05 24 30 40 00 b9 00 00 00 00 f3 0f 10 1d 20 30
  4010d0 40 00 f3 0f 10 25 24 30 40 00 f3 0f 10 c3 f3 0f
  4010e0 10 cc f3 0f 10 15 28 30 40 00 f3 0f 10 e8 f3 0f
  4010f0 10 f1 f3 0f 59 ed f3 0f 59 f6 f3 0f 10 fd f3 0f
  401100 58 fe 0f 2f fa 0f 83 2b 00 00 00 f3 0f 5c ee f3
  401110 0f 58 eb f3 0f 59 c8 f3 0f 58 c9 f3 0f 58 cc f3
  401120 0f 10 c5 41 81 f9 00 01 00 00 0f 8c be ff ff ff
  401130 b9 00 00 ff 00 c3 50 89 c8 c1 e0 08 01 c8 c1 e0
  401140 08 01 c8 89 c1 58 c3 50 68 2c 30 40 00 ff 15 88
  401150 23 40 00 58 58 c3 8b 44 24 04 a3 3d 30 40 00 a1
  401160 3d 30 40 00 3b 05 41 30 40 00 0f 85 05 00 00 00
  401170 e8 d2 ff ff ff c3 f3 0f 10 0d 08 30 40 00 f3 0f
  401180 10 15 45 30 40 00 f3 0f 59 ca f3 0f 11 0d 08 30
  401190 40 00 f3 0f 10 0d 0c 30 40 00 f3 0f 10 15 45 30
  4011a0 40 00 f3 0f 59 ca f3 0f 11 0d 0c 30 40 00 c3 8b
  4011b0 44 24 04 a3 49 30 40 00 e8 8a ff ff ff 8b 44 24
  4011c0 08 a3 4d 30 40 00 e8 7c ff ff ff a1 49 30 40 00
  4011d0 f3 0f 2a c8 a1 54 23 40 00 8b 18 f3 0f 2a d3 f3
  4011e0 0f 5e ca f3 0f 59 0d 08 30 40 00 f3 0f 58 0d 00
  4011f0 30 40 00 f3 0f 10 15 08 30 40 00 b8 fe ff ff ff
  401200 f3 0f 2a d8 f3 0f 5e d3 f3 0f 58 ca f3 0f 11 0d
  401210 00 30 40 00 a1 4d 30 40 00 f3 0f 2a c8 a1 58 23
  401220 40 00 8b 18 f3 0f 2a d3 f3 0f 5e ca f3 0f 59 0d
  401230 0c 30 40 00 f3 0f 58 0d 04 30 40 00 f3 0f 10 15
  401240 0c 30 40 00 b8 fe ff ff ff f3 0f 2a d8 f3 0f 5e
  401250 d3 f3 0f 58 ca f3 0f 11 0d 04 30 40 00 f3 0f 10
  401260 0d 08 30 40 00 f3 0f 10 15 51 30 40 00 f3 0f 5e
  401270 ca f3 0f 11 0d 08 30 40 00 f3 0f 10 0d 0c 30 40
  401280 00 f3 0f 10 15 51 30 40 00 f3 0f 5e ca f3 0f 11
  401290 0d 0c 30 40 00 c3 c3 c3 68 00 70 00 00 ff 15 5c
  4012a0 23 40 00 58 e8 5c fd ff ff a1 60 23 40 00 8b 28
  4012b0 a1 54 23 40 00 8b 18 a1 58 23 40 00 8b 10 bf 00
  4012c0 00 00 00 be 00 00 00 00 52 89 f8 f7 e3 01 f0 c1
  4012d0 e0 02 01 e8 5a e8 ab fd ff ff 89 08 46 39 de 0f
  4012e0 8c e3 ff ff ff 47 39 d7 0f 8c d5 ff ff ff c3 68
  4012f0 97 12 40 00 ff 15 64 23 40 00 58 68 af 11 40 00
  401300 ff 15 68 23 40 00 58 68 76 11 40 00 ff 15 6c 23
  401310 40 00 58 68 56 11 40 00 ff 15 70 23 40 00 58 68
  401320 96 12 40 00 ff 15 74 23 40 00 58 68 98 12 40 00
  401330 ff 15 78 23 40 00 58 68 0a 00 00 00 ff 15 7c 23
  401340 40 00 58 68 e0 01 00 00 68 80 02 00 00 68 e0 01
  401350 00 00 68 80 02 00 00 68 14 00 00 00 68 14 00 00
  401360 00 68 55 30 40 00 ff 15 80 23 40 00 83 c4 14 b8
  401370 00 00 00 00 c3
------------------------------------------------------------------------------
 Filing PE Header:  
------------------------------------------------------------------------------
 Verbose PE header settings:  (all numbers in hex)

 --- sizeof IMAGE_DOS_HEADER  <0040> --------------- 
 
 magic                    <5a4d> 
 pe ofset in file         <0080> 
 sizeof dos stub[]        <0040> 

 --- sizeof IMAGE_NT_HEADERS  <00f8> --------------- 
 
 signature                <4550> 

 --- sizeof IMAGE_FILE_HEADER <0014> --------------- 
 
 machine                <014c> 
 number of sections     <0003> 
 time date stamp        <5e0be100> 
 opt. header size set   <00e0> 
 characteristics        <0307> 

 --- sizeof IMAGE_OPTIONAL_HEADER <00e0> ----------- 
 
 major linker           <0002>  minor linker <0000> 
 size of code set       <0400> 
 size of init. data set <0200> 
 size of unit. data set <0000> 
 adres of entry point   <1000> 
 base of code           <1000> 
 base of data           <3000> 
 image base             <400000> 
 section aligment       <1000> 
 file aligment          <0200> 
 major os ver           <0004>  minor os ver  <0000> 
 major image ver        <0001>  minor image ver  <0000> 
 major subsystem ver    <0004>  minor subsystem ver  <0000> 
 win32 version value    <0000> 
 size of image          <4000> 
 size of headers        <0200> 
 checksum               <0000> 
 subsystem              <0002> 
 size of stack reserve  <200000>  size of stack sommit  <1000> 
 size of heap reserve   <100000>  size of heap commit  <1000> 
 loader flags           <0000> 

 no. of rva and sizes   <0010> 
 DD[01] virtual adress  <2000>  DD[01] size  <0390> 
 DD[12] virtual adress  <2354>  DD[12] size  <0040> 

 --- sizeof IMAGE_SECTION_HEADER <0028> ------------ 
 
 sec1 name            .text  
 virtual size         <0375> 
 virtual sdress       <1000> 
 size of raw data     <0400> 
 pointer to raw data  <0200> 
 characteristics      <60000020> 

 sec2 name            .idata  
 virtual size         <0390> 
 virtual sdress       <2000> 
 size of raw data     <0400> 
 pointer to raw data  <0600> 
 characteristics      <40000040> 

 sec3 name            .data
virtual size         <1000>
 virtual sdress       <3000> 
 size of raw data     <0200> 
 pointer to raw data  <0a00> 
 characteristics      <c0000040> 

 -- offsets in saved file: ------------------------- 
 
 dosHeader:               <0000> dos_stub: <0040>
 ntHeader:                <0080> header: <0084> opHeader: <0098>
 sectionheaderCode:       <0178>
 sectionheaderImports:    <01a0>
 sectionheaderData:       <01c8>

 code section file ofset:    <0200> size: <0400>
 imports section file ofset: <0600> size: <0400>
 data section file ofset:    <0a00> size: <0200>
 file end:                   <0bff> 
------------------------------------------------------------------------------
 
------------------------------------------------------------------------------
 Output Saved:  result2.exe 
------------------------------------------------------------------------------
 OK  (assembled in 0.007 s)
------------------------------------------------------------------------------

[toc] | [prev] | [next] | [standalone]


#171205

FromRichard Harnden <richard.nospam@gmail.com>
Date2023-07-24 13:45 +0100
Message-ID<u9lrpj$line$1@dont-email.me>
In reply to#171204
On 24/07/2023 13:19, fir wrote:
> poniedziałek, 24 lipca 2023 o 14:10:54 UTC+2 fir napisał(a):
>> i wrote my own assembler (org-asm) you my check it
>>
>> https://fastupload.io/CYnB7m6CLilssjs/file
>>
>> it compiles 3 examples...the attached dll is to run second example and thsi ddl is for opening window which my exampel ina ssembly calls to draw mandelbrot set
>>
>> hovever the resulted exe is simple and has no exception section which may be reason windows defender or other programs can false identify it as malvare it is strictly what you code in asm only
> 
> you may se the nice output log from it
> 
> 
> +----------------------------------------------------------------------------+
> |                                                                            |
> | Organic Assembler (org-asm) by fir, december of 2020    (;ast update V.22) |
                                                              ^
                                                              |
You can't even avoid typos in your own readmes --------------+

Jeez.

> |                                                                            |
> | note: this is  early version with far from elaborate                       |
> | error messages and not strictly all of the mnemonics implemented,          |
> | hovever it does the work and i find it nice and usefull                    |
> |                                                                            |
> | right now it is able to assemble win32/x86 exe files (no output as dll     |
> | yet) with any possible dll imports, so youre basicaly able to assemble     |
> | any win32 app with it                                                      |

Also, the shift key is only an inch away.  Please learn to spend that 
extra fraction of a second.

[toc] | [prev] | [next] | [standalone]


#171206

Fromfir <profesor.fir@gmail.com>
Date2023-07-24 05:51 -0700
Message-ID<1473a1e7-0751-408f-b920-eec9178f9271n@googlegroups.com>
In reply to#171205
poniedziałek, 24 lipca 2023 o 14:45:54 UTC+2 Richard Harnden napisał(a):
> On 24/07/2023 13:19, fir wrote: 
> > poniedziałek, 24 lipca 2023 o 14:10:54 UTC+2 fir napisał(a): 
> >> i wrote my own assembler (org-asm) you my check it 
> >> 
> >> https://fastupload.io/CYnB7m6CLilssjs/file 
> >> 
> >> it compiles 3 examples...the attached dll is to run second example and thsi ddl is for opening window which my exampel ina ssembly calls to draw mandelbrot set 
> >> 
> >> hovever the resulted exe is simple and has no exception section which may be reason windows defender or other programs can false identify it as malvare it is strictly what you code in asm only 
> > 
> > you may se the nice output log from it 
> > 
> > 
> > +----------------------------------------------------------------------------+ 
> > | | 
> > | Organic Assembler (org-asm) by fir, december of 2020 (;ast update V.22) |
> ^ 
> | 
> You can't even avoid typos in your own readmes --------------+ 
> 
> Jeez.

i dont care that much - note thet logic structure of this log is high,
and that cominicates what is not done i will delete if i do what is not done (hovever presently i not work on this assembler hovever i like it,
it went well)

> > | | 
> > | note: this is early version with far from elaborate | 
> > | error messages and not strictly all of the mnemonics implemented, | 
> > | hovever it does the work and i find it nice and usefull | 
> > | | 
> > | right now it is able to assemble win32/x86 exe files (no output as dll | 
> > | yet) with any possible dll imports, so youre basicaly able to assemble | 
> > | any win32 app with it |
> Also, the shift key is only an inch away. Please learn to spend that 
> extra fraction of a second.

[toc] | [prev] | [next] | [standalone]


#171209

Fromfir <profesor.fir@gmail.com>
Date2023-07-24 06:44 -0700
Message-ID<b16208a2-c862-4aa5-9f38-fd7562c186can@googlegroups.com>
In reply to#171206
poniedziałek, 24 lipca 2023 o 14:51:34 UTC+2 fir napisał(a):
> poniedziałek, 24 lipca 2023 o 14:45:54 UTC+2 Richard Harnden napisał(a): 
> > On 24/07/2023 13:19, fir wrote: 
> > > poniedziałek, 24 lipca 2023 o 14:10:54 UTC+2 fir napisał(a): 
> > >> i wrote my own assembler (org-asm) you my check it 
> > >> 
> > >> https://fastupload.io/CYnB7m6CLilssjs/file 
> > >> 
> > >> it compiles 3 examples...the attached dll is to run second example and thsi ddl is for opening window which my exampel ina ssembly calls to draw mandelbrot set 
> > >> 
> > >> hovever the resulted exe is simple and has no exception section which may be reason windows defender or other programs can false identify it as malvare it is strictly what you code in asm only 
> > > 
> > > you may se the nice output log from it 
> > > 
> > > 
> > > +----------------------------------------------------------------------------+ 
> > > | | 
> > > | Organic Assembler (org-asm) by fir, december of 2020 (;ast update V.22) | 
> > ^ 
> > | 
> > You can't even avoid typos in your own readmes --------------+ 
> > 
> > Jeez.
> i dont care that much - note thet logic structure of this log is high, 
> and that cominicates what is not done i will delete if i do what is not done (hovever presently i not work on this assembler hovever i like it, 
> it went well)
> > > | | 
> > > | note: this is early version with far from elaborate | 
> > > | error messages and not strictly all of the mnemonics implemented, | 
> > > | hovever it does the work and i find it nice and usefull | 
> > > | | 
> > > | right now it is able to assemble win32/x86 exe files (no output as dll | 
> > > | yet) with any possible dll imports, so youre basicaly able to assemble | 
> > > | any win32 app with it | 
> > Also, the shift key is only an inch away. Please learn to spend that 
> > extra fraction of a second.

maybe fractions of seconds of your time had no value but not mine

btw i got no motivation tu upbuild this asembler (mostly needed error communicates, dll output and x64 version) as nobody uses it, it is not in the net though

i would need tu make some www page it to be able to download and make soeme adress to send demands for upgrades...if someone would hacve space on his ww page i would like to use it

[toc] | [prev] | [next] | [standalone]


#171212

FromRichard Harnden <richard.nospam@gmail.com>
Date2023-07-24 15:36 +0100
Message-ID<u9m29l$mtpl$1@dont-email.me>
In reply to#171209
On 24/07/2023 14:44, fir wrote:
> poniedziałek, 24 lipca 2023 o 14:51:34 UTC+2 fir napisał(a):
>> poniedziałek, 24 lipca 2023 o 14:45:54 UTC+2 Richard Harnden napisał(a):
>>> On 24/07/2023 13:19, fir wrote:
>>>> poniedziałek, 24 lipca 2023 o 14:10:54 UTC+2 fir napisał(a):
>>>>> i wrote my own assembler (org-asm) you my check it
>>>>>
>>>>> https://fastupload.io/CYnB7m6CLilssjs/file
>>>>>
>>>>> it compiles 3 examples...the attached dll is to run second example and thsi ddl is for opening window which my exampel ina ssembly calls to draw mandelbrot set
>>>>>
>>>>> hovever the resulted exe is simple and has no exception section which may be reason windows defender or other programs can false identify it as malvare it is strictly what you code in asm only
>>>>
>>>> you may se the nice output log from it
>>>>
>>>>
>>>> +----------------------------------------------------------------------------+
>>>> | |
>>>> | Organic Assembler (org-asm) by fir, december of 2020 (;ast update V.22) |
>>> ^
>>> |
>>> You can't even avoid typos in your own readmes --------------+
>>>
>>> Jeez.
>> i dont care that much - note thet logic structure of this log is high,
>> and that cominicates what is not done i will delete if i do what is not done (hovever presently i not work on this assembler hovever i like it,
>> it went well)
>>>> | |
>>>> | note: this is early version with far from elaborate |
>>>> | error messages and not strictly all of the mnemonics implemented, |
>>>> | hovever it does the work and i find it nice and usefull |
>>>> | |
>>>> | right now it is able to assemble win32/x86 exe files (no output as dll |
>>>> | yet) with any possible dll imports, so youre basicaly able to assemble |
>>>> | any win32 app with it |
>>> Also, the shift key is only an inch away. Please learn to spend that
>>> extra fraction of a second.
> 
> maybe fractions of seconds of your time had no value but not mine

So, instead of spending a little time yourself you expect 1000s of 
readers to spend their own time?

> 
> btw i got no motivation tu upbuild this asembler (mostly needed error communicates, dll output and x64 version) as nobody uses it, it is not in the net though

That's okay because nobody has any motivation to use your assembler.


[toc] | [prev] | [next] | [standalone]


#171214

Fromfir <profesor.fir@gmail.com>
Date2023-07-24 07:40 -0700
Message-ID<5be09eca-40a1-4cbb-b7dd-035a9b70b642n@googlegroups.com>
In reply to#171212
poniedziałek, 24 lipca 2023 o 16:36:52 UTC+2 Richard Harnden napisał(a):
> On 24/07/2023 14:44, fir wrote: 
> > poniedziałek, 24 lipca 2023 o 14:51:34 UTC+2 fir napisał(a): 
> >> poniedziałek, 24 lipca 2023 o 14:45:54 UTC+2 Richard Harnden napisał(a): 
> >>> On 24/07/2023 13:19, fir wrote: 
> >>>> poniedziałek, 24 lipca 2023 o 14:10:54 UTC+2 fir napisał(a): 
> >>>>> i wrote my own assembler (org-asm) you my check it 
> >>>>> 
> >>>>> https://fastupload.io/CYnB7m6CLilssjs/file 
> >>>>> 
> >>>>> it compiles 3 examples...the attached dll is to run second example and thsi ddl is for opening window which my exampel ina ssembly calls to draw mandelbrot set 
> >>>>> 
> >>>>> hovever the resulted exe is simple and has no exception section which may be reason windows defender or other programs can false identify it as malvare it is strictly what you code in asm only 
> >>>> 
> >>>> you may se the nice output log from it 
> >>>> 
> >>>> 
> >>>> +----------------------------------------------------------------------------+ 
> >>>> | | 
> >>>> | Organic Assembler (org-asm) by fir, december of 2020 (;ast update V.22) | 
> >>> ^ 
> >>> | 
> >>> You can't even avoid typos in your own readmes --------------+ 
> >>> 
> >>> Jeez. 
> >> i dont care that much - note thet logic structure of this log is high, 
> >> and that cominicates what is not done i will delete if i do what is not done (hovever presently i not work on this assembler hovever i like it, 
> >> it went well) 
> >>>> | | 
> >>>> | note: this is early version with far from elaborate | 
> >>>> | error messages and not strictly all of the mnemonics implemented, | 
> >>>> | hovever it does the work and i find it nice and usefull | 
> >>>> | | 
> >>>> | right now it is able to assemble win32/x86 exe files (no output as dll | 
> >>>> | yet) with any possible dll imports, so youre basicaly able to assemble | 
> >>>> | any win32 app with it | 
> >>> Also, the shift key is only an inch away. Please learn to spend that 
> >>> extra fraction of a second. 
> > 
> > maybe fractions of seconds of your time had no value but not mine
> So, instead of spending a little time yourself you expect 1000s of 
> readers to spend their own time?
> > 

they may activate their brain (if they get one)

> > btw i got no motivation tu upbuild this asembler (mostly needed error communicates, dll output and x64 version) as nobody uses it, it is not in the net though
> That's okay because nobody has any motivation to use your assembler.

[toc] | [prev] | [next] | [standalone]


#171211

Fromfir <profesor.fir@gmail.com>
Date2023-07-24 07:29 -0700
Message-ID<9da72e18-db26-4d6e-9059-1d9424b2d8aan@googlegroups.com>
In reply to#171206
poniedziałek, 24 lipca 2023 o 14:51:34 UTC+2 fir napisał(a):
> poniedziałek, 24 lipca 2023 o 14:45:54 UTC+2 Richard Harnden napisał(a): 
> > On 24/07/2023 13:19, fir wrote: 
> > > poniedziałek, 24 lipca 2023 o 14:10:54 UTC+2 fir napisał(a): 
> > >> i wrote my own assembler (org-asm) you my check it 
> > >> 
> > >> https://fastupload.io/CYnB7m6CLilssjs/file 
> > >> 
> > >> it compiles 3 examples...the attached dll is to run second example and thsi ddl is for opening window which my exampel ina ssembly calls to draw mandelbrot set 
> > >> 
> > >> hovever the resulted exe is simple and has no exception section which may be reason windows defender or other programs can false identify it as malvare it is strictly what you code in asm only 
> > > 
> > > you may se the nice output log from it 
> > > 
> > > 
> > > +----------------------------------------------------------------------------+ 
> > > | | 
> > > | Organic Assembler (org-asm) by fir, december of 2020 (;ast update V.22) | 
> > ^ 
> > | 
> > You can't even avoid typos in your own readmes --------------+ 
> > 
> > Jeez.
> i dont care that much - note thet logic structure of this log is high, 
> and that cominicates what is not done i will delete if i do what is not done (hovever presently i not work on this assembler hovever i like it, 
> it went well)
> > > | | 
> > > | note: this is early version with far from elaborate | 
> > > | error messages and not strictly all of the mnemonics implemented, | 
> > > | hovever it does the work and i find it nice and usefull | 
> > > | | 
> > > | right now it is able to assemble win32/x86 exe files (no output as dll | 
> > > | yet) with any possible dll imports, so youre basicaly able to assemble | 
> > > | any win32 app with it | 
> > Also, the shift key is only an inch away. Please learn to spend that 
> > extra fraction of a second.

i could rather improve the log for example denote the adresses

if end of this code is

203 (l. 353) push 20 
204 (l. 353) push 20 
205 (l. 354) push title 
206 (l. 354) call (green.fire.dll->SetupWindow3) 
207 (l. 355) add esp 20 
208 (l. 357) mov eax 0 
209 (l. 358) ret 

and end of binary is 
401350 00 00 68 80 02 00 00 68 14 00 00 00 68 14 00 00 
401360 00 68 55 30 40 00 ff 15 80 23 40 00 83 c4 14 b8 
401370 00 00 00 00 c3 

should mark it some way 
401350 00 00/68\80 02 00 00/68\14 00 00 00/68\14 00 00 
401360 00/68\55 30 40 00/ff 15\80 23 40 00/83 c4\14/b8\ 
401370 00 00 00 00/c3

or maybe something more readable...im not sure if the code is compatible to flush this without bigger changes

[toc] | [prev] | [next] | [standalone]


#171213

Fromfir <profesor.fir@gmail.com>
Date2023-07-24 07:39 -0700
Message-ID<6118d648-f4e2-4550-8f69-7ea6183b98d0n@googlegroups.com>
In reply to#171211
poniedziałek, 24 lipca 2023 o 16:29:21 UTC+2 fir napisał(a):
> poniedziałek, 24 lipca 2023 o 14:51:34 UTC+2 fir napisał(a):
> > poniedziałek, 24 lipca 2023 o 14:45:54 UTC+2 Richard Harnden napisał(a): 
> > > extra fraction of a second.
> i could rather improve the log for example denote the adresses 
> 
> if end of this code is
> 203 (l. 353) push 20 
> 204 (l. 353) push 20 
> 205 (l. 354) push title 
> 206 (l. 354) call (green.fire.dll->SetupWindow3) 
> 207 (l. 355) add esp 20 
> 208 (l. 357) mov eax 0 
> 209 (l. 358) ret
> and end of binary is
> 401350 00 00 68 80 02 00 00 68 14 00 00 00 68 14 00 00 
> 401360 00 68 55 30 40 00 ff 15 80 23 40 00 83 c4 14 b8 
> 401370 00 00 00 00 c3
> should mark it some way 
> 401350 00 00/68\80 02 00 00/68\14 00 00 00/68\14 00 00 
> 401360 00/68\55 30 40 00/ff 15\80 23 40 00/83 c4\14/b8\ 
> 401370 00 00 00 00/c3 
> 
> or maybe something more readable...im not sure if the code is compatible to flush this without bigger changes

or maybe something liek that or somethin

 401350 00 00(68)80:02:00:00(68)14:00:00:00(68)14:00:00: 
 401360 00(68)55:30:40:00(ff/15)80:23:40:00(83/c4)14(b8)
 401370 00:00:00:00(c3)

i remembered though i flush thsi binary code just as bytes in array so i would need to modify and ad array for tags

[toc] | [prev] | [next] | [standalone]


#171237

Fromfir <profesor.fir@gmail.com>
Date2023-07-25 02:34 -0700
Message-ID<1b620d34-c717-40b2-a9bb-e6b1693592f8n@googlegroups.com>
In reply to#171211
poniedziałek, 24 lipca 2023 o 16:29:21 UTC+2 fir napisał(a):
> poniedziałek, 24 lipca 2023 o 14:51:34 UTC+2 fir napisał(a):
> > poniedziałek, 24 lipca 2023 o 14:45:54 UTC+2 Richard Harnden napisał(a): 
> > > On 24/07/2023 13:19, fir wrote: 
> > > > poniedziałek, 24 lipca 2023 o 14:10:54 UTC+2 fir napisał(a): 
> > > >> i wrote my own assembler (org-asm) you my check it 
> > > >> 
> > > >> https://fastupload.io/CYnB7m6CLilssjs/file 
> > > >> 
> > > >> it compiles 3 examples...the attached dll is to run second example and thsi ddl is for opening window which my exampel ina ssembly calls to draw mandelbrot set 
> > > >> 
> > > >> hovever the resulted exe is simple and has no exception section which may be reason windows defender or other programs can false identify it as malvare it is strictly what you code in asm only 
> > > > 
> > > > you may se the nice output log from it 
> > > > 
> > > > 
> > > > +----------------------------------------------------------------------------+ 
> > > > | | 
> > > > | Organic Assembler (org-asm) by fir, december of 2020 (;ast update V.22) | 
> > > ^ 
> > > | 
> > > You can't even avoid typos in your own readmes --------------+ 
> > > 
> > > Jeez. 
> > i dont care that much - note thet logic structure of this log is high, 
> > and that cominicates what is not done i will delete if i do what is not done (hovever presently i not work on this assembler hovever i like it, 
> > it went well) 
> > > > | | 
> > > > | note: this is early version with far from elaborate | 
> > > > | error messages and not strictly all of the mnemonics implemented, | 
> > > > | hovever it does the work and i find it nice and usefull | 
> > > > | | 
> > > > | right now it is able to assemble win32/x86 exe files (no output as dll | 
> > > > | yet) with any possible dll imports, so youre basicaly able to assemble | 
> > > > | any win32 app with it | 
> > > Also, the shift key is only an inch away. Please learn to spend that 
> > > extra fraction of a second.
> i could rather improve the log for example denote the adresses 
> 
> if end of this code is
> 203 (l. 353) push 20 
> 204 (l. 353) push 20 
> 205 (l. 354) push title 
> 206 (l. 354) call (green.fire.dll->SetupWindow3) 
> 207 (l. 355) add esp 20 
> 208 (l. 357) mov eax 0 
> 209 (l. 358) ret
> and end of binary is
> 401350 00 00 68 80 02 00 00 68 14 00 00 00 68 14 00 00 
> 401360 00 68 55 30 40 00 ff 15 80 23 40 00 83 c4 14 b8 
> 401370 00 00 00 00 c3
> should mark it some way 
> 401350 00 00/68\80 02 00 00/68\14 00 00 00/68\14 00 00 
> 401360 00/68\55 30 40 00/ff 15\80 23 40 00/83 c4\14/b8\ 
> 401370 00 00 00 00/c3 
> 
> or maybe something more readable...im not sure if the code is compatible to flush this without bigger changes

this log is important coz imo assembly is not just writting in assembly but "totall transparency" clearly seen what is goin on to the bone

[toc] | [prev] | [next] | [standalone]


#171183

FromVir Campestris <vir.campestris@invalid.invalid>
Date2023-07-23 20:48 +0100
Message-ID<u9k061$b57v$1@dont-email.me>
In reply to#171176
On 23/07/2023 19:32, Bonita Montero wrote:
> For sure in assembly, because that's easier to learn than C. 😉

Yes, but which assembler?

I've used perhaps a dozen. Perhaps because it depends on things like 
whether a '286 counts as different to an 8086.

I have no clue how many lines of code I've written. Not even the vaguest 
idea.

Andy

[toc] | [prev] | [next] | [standalone]


#171184

Fromfir <profesor.fir@gmail.com>
Date2023-07-23 13:29 -0700
Message-ID<63c3d7e2-132b-4fc8-84cd-6d665cd5110bn@googlegroups.com>
In reply to#171183
niedziela, 23 lipca 2023 o 21:48:30 UTC+2 Vir Campestris napisał(a):
> On 23/07/2023 19:32, Bonita Montero wrote: 
> > For sure in assembly, because that's easier to learn than C. 😉 
> 
> Yes, but which assembler? 
> 
> I've used perhaps a dozen. Perhaps because it depends on things like 
> whether a '286 counts as different to an 8086. 
> 
> I have no clue how many lines of code I've written. Not even the vaguest 
> idea. 
> 
cound your average lines written in month then count the monyhs (but take all the holes in coding in consideration) but do the counting properly - not rise up... the lines i count by taking kilobytes written and dividing by 20 as average length of a line

[toc] | [prev] | [next] | [standalone]


#171191

FromDavid Brown <david.brown@hesbynett.no>
Date2023-07-24 09:02 +0200
Message-ID<u9l7m1$it9v$1@dont-email.me>
In reply to#171183
On 23/07/2023 21:48, Vir Campestris wrote:
> On 23/07/2023 19:32, Bonita Montero wrote:
>> For sure in assembly, because that's easier to learn than C. 😉
> 
> Yes, but which assembler?
> 
> I've used perhaps a dozen. Perhaps because it depends on things like 
> whether a '286 counts as different to an 8086.
> 

I have also used at least a dozen assembly languages - and that is /not/ 
counting variations such as 8086/80286.  (I haven't actually written any 
x86 assembly.)

And while some are easy to learn, others are very far from simple - 
especially if you want to get efficient results.

> I have no clue how many lines of code I've written. Not even the vaguest 
> idea.
> 
> Andy
> 

[toc] | [prev] | [next] | [standalone]


#171192

Fromfir <profesor.fir@gmail.com>
Date2023-07-24 00:27 -0700
Message-ID<f8b720c1-aa44-4323-9347-1615860b17e2n@googlegroups.com>
In reply to#171191
poniedziałek, 24 lipca 2023 o 09:02:40 UTC+2 David Brown napisał(a):
> On 23/07/2023 21:48, Vir Campestris wrote: 
> > On 23/07/2023 19:32, Bonita Montero wrote: 
> >> For sure in assembly, because that's easier to learn than C. 😉 
> > 
> > Yes, but which assembler? 
> > 
> > I've used perhaps a dozen. Perhaps because it depends on things like 
> > whether a '286 counts as different to an 8086. 
> >
> I have also used at least a dozen assembly languages - and that is /not/ 
> counting variations such as 8086/80286. (I haven't actually written any 
> x86 assembly.) 
> 
> And while some are easy to learn, others are very far from simple - 
> especially if you want to get efficient results.
> > I have no clue how many lines of code I've written. Not even the vaguest 
> > idea. 
> > 

code is a tree assembler is good for the 'leafs' but not for the composition of thousands of them (today compiler manages the leafs).. i n fact is better to manage the thin branches (wtwigs) but i
think from some time it has a lack of the bigger branches..
im not sure in quite new part of the language wouldnt be needed
(to ba able to manage those twigs)

one think is the big picture of code in c is not clearly showed,
the second is sometimes someone need to write a big doze
of switches which is tiring and probbaly it would be better to have some pattern for this 

[toc] | [prev] | [next] | [standalone]


Page 1 of 4  [1] 2 3 4  Next page →

Back to top | Article view | comp.lang.c


csiph-web