Author Topic: JWasm continuation (our try) on GitHub  (Read 4304 times)

GoneFishing

  • Member
  • ****
  • Posts: 950
  • Gone fishing
Re: JWasm continuation (our try) on GitHub
« Reply #15 on: November 11, 2015, 06:19:33 AM »
Hi Vortex,
Yes , I know . I read that thread and got a strong feeling that it was not Andreas but a trickster .
Lexicon and formatting of words  made me think so.
Though maybe I'm wrong and  my intuition plays tricks to me...

One more argument proving my wild guess  - his avatar image named Britney_Spears !
Google image search for this picture shows that it's taken  from the standart avatar set for forums . Who has such packages? Serious programmers like Andreas? Unlikely .
Goal?
Advertisement.



xanatose

  • Member
  • ***
  • Posts: 370
Re: JWasm continuation (our try) on GitHub
« Reply #16 on: November 27, 2015, 05:54:40 PM »
Could it be possible to add
-nologo

or

-quiet

to suppress any output unless there is an error?

milabs

  • Regular Member
  • *
  • Posts: 2
Re: JWasm continuation (our try) on GitHub
« Reply #17 on: December 03, 2015, 06:38:27 PM »
xanatose, sure. Just add the issue to https://github.com/JWasm/JWasm/issues

hutch--

  • Administrator
  • Member
  • ******
  • Posts: 4807
  • Mnemonic Driven API Grinder
    • The MASM32 SDK
Re: JWasm continuation (our try) on GitHub
« Reply #18 on: December 06, 2015, 03:38:24 PM »
I guess my cynicism is showing but there was a good reason why I posted Japheth's version at the top of the page, its so folks know where the development started and stopped. While I have no doubt that various folks have done work on the source code after Japheth abandoned the project, with multiple versions you end up with a "Forked fork of a forked fork" (all puns intended).
hutch at movsd dot com
http://www.masm32.com    :biggrin:  :biggrin:

ACP

  • Regular Member
  • *
  • Posts: 10
Re: JWasm continuation (our try) on GitHub
« Reply #19 on: December 11, 2015, 04:08:03 AM »
Exactly my thoughts from few posts earlier. Anyway I wish you guys luck. Seems like putting the project on github, splitting regression tests and enabling ticket tracking is a good start, but you guys still need to somehow invite others from separate forks to cooperate. Otherwise we really may end up with a number of JWASM based assemblers with different syntax. I guess we have already large enough base of different syntaxes for x86/x64 so creating new set on already well established assembler will not help anyone in long turn.
ASM beyond Repair https://corexor.wordpress.com blog about assembly related stuff