686:) you will see that while it is intended to be MASM compatible, it is lacking in a number of features. On the other hand JWasm is in active development (v2.02 was released Jan. 19, 2010), supports almost every feature of MASM, supports all x86 instructions (IA32 and Intel 64 and all SIMD instructions to date), it has builds for Win32, DOS and Linux, can generate OMF, COFF, and DOS binaries (COM and EXE) and it is open source. To someone who is actually an Intel x86 assembly language programmer, JWasm is quite notable indeed. Keep in mind that MASM is the de-facto standard for x86 assembly language so an open source assembler with a very high degree of MASM compatibility is definitely worthy of note. The same can not be said for several of the other obscure assemblers which have articles (e.g. FASM, YASM, HLA). Why does YASM which is a fork of NASM have its own article but not JWasm ? That seems quite arbitrary and frankly hypocritical. -- 99.186.40.14 06:56, 17 February 2010.
436:" which is neither review not reference material. Now instead of clutching at straws you need to deliver what is required for the notability of WASM to be established. If it is as you say notable then you will supply the material that demonstrates that it is notable. WASM is not a competitor to anything these days and your attempts at analysis here are unsound. Now instead of clutching at straws posting junk like the stuff so far, please produce the appropriate technical reference and review to demonstrate that WASM is notable so this page can move on. Also you need to understand that predictions are best done with a crystal ball and not try and predict things that simply does not exist.
560:
including HLA which isn't even a true assembler so how is notability determined ? Clearly MASM (Microsoft Macro
Assembler) is notable as it is the standard x86 assembler and is still maintained. TASM (Borland Turbo Assembler) is notable as it was a commercial product. GAS (GNU Assembler) is notable for being a standard in the Linux/Unix world. An argument for the notability of JWASM is the fact that it is an open-source alternative to MASM with a very high compatibility to MASM syntax and can process almost all source files which MASM can which is something the other minor assemblers can't do.
691:
Assembler posted on a defunct teaching site. They have contented themselves that this crap justifies keeping Open Watcom
Assembler as an article but not JWASM. They have no criterion to say what notability is in the specialist field of assembly programming. They applied the literal criteria supplied by the Wiki's guidelines for notability, rather than admitting that they didn't know what notability was in this case. However, once such a decision has been made, they are on to the next article to delete or keep and the results are set in stone. --
99:
81:
50:
398:. And it covers both WASM and JWASM, so a continuity does exist in a source, and his opinions are relevant (although not yet included in this article). When JWASM will be covered in more independent sources that Fog's book, it will be possible have an article about it (again). Since you are somewhat of an authority in this field, you could have an article published about JWASM in a
754:) our rules then go away." (parenthesis added) You've helped drive off an expert in the field of assembly language programming. Now you are saying if someone doesn't like your interpretations of the rules, they can go away. Then you categorize people who disagree with you as "ranting disruptively". Finally, you threaten people with being banned. Who needs this? --
21:
823:
Have you quite finished with your personal attacks, harassment and disruptive behaviour? If you actually want to change anything, you have to follow our processes. If either of you continue with this behaviour (I assume the changing IP user is the same person each time) then I will not grace you with
348:
The opening statement in the page has a discontinuity where there is no association between the old WASM and the later JWASM. The association needs to be cited otherwise the reference to JWASM has no context. Would the editors who have taken over the task of writing the WASM-JWASM page now supply the
342:
The insertion of the work by Agner Fog is inappropriate, it is titled "Optimizing subroutines in assembly language" and addresses exactly that topic, it is not written as a review of different assembler and it states no more than Agner Fogs preference in assembler and a casual listing of the onces he
999:
Also, if you click "Comments, Suggestions, and
Contact Info" you are taken to Mr Hyde's contact details. There is nothing to suggest that he did not write that blurb. You are the one scrabbling around desperately trying to find a reason to delete the page. The irony is that it only exists because of
601:
Our anonymous editor seems to have found this response unhelpful. Pcap's insistence on maintaining this unexplanatory comment is typical of the unexplained keeping of this article whose main reason for existence seems to be to supply a reference to JWASM that the people, who voted to keep this page,
920:
Although there is a reference in the article attributed to
Randall Hyde, the text itself when viewed from the link is unattributed, though the site does feature Randall Hyde's book on assembly language. There is no way of knowing who actually wrote the distribution blurb for WASM and it cannot be
852:
So your measure of notability is essentially a Google search ? FASM, HLA and YASM are obscure assemblers which aren't even MASM compatible and HLA isn't even a true assembler. If you are really versed in the subject as you claim you are then you know that MASM is the standard for x86 assemblers so
1020:
Are you so totally incapable of showing who actually wrote the material you are citing as a reliable third party source that you have to play such games? You don't mind citing an unattributed blurb on an unmaintained site whose contact information comes back to
Randall Hyde. Did he write it? You
880:
Bottom line here is you and Pohta-whatever singled out one particular assembler to delete the article for while you left the others intact and this come across as a personal bias of some sort. Anyway why does it bother you so much if there is a JWasm article ? Obviously it shouldn't be a cut and
559:
Why is WASM considered notable enough to have an article but JWASM is not ? While JWASM is a fork of WASM it is in active development and a much more mature program than WASM which no longer appears to be in development. Likewise several other obscure and minor assemblers have their own articles
690:
The people who killed JWASM have contented themselves to keep Open Watcom
Assembler on a few paltry indications cribbed together from a text that barely mentions Open Watcom Assembler, a book that also mentions JWASM and an old unprovenanced internet blurb for the distribution of Open Watcom
892:
The template for x86 assemblers was constructed from all the available topics in the field at the time. There was nothing deep about the choice of material; it was: use everything available on
Knowledge (XXG). That included JWASM and a number of other assemblers mentioned in the
681:
OrangeDog and Pohta-whatever (both foolish names by the way) are typical WikiDrones™ who blindly regurgitate rules and likely have no real knowledge of the subject matter. WASM has not been updated in years and if you look the
Current State section on Watcom's site
656:
When Wiki politicians join together to keep a fossil article they'll never improve, is there any point in disputing the decision? And the thing is, OrangeDog, you know that it will never be improved and that it will remain just a vestigial reference to JWASM. --
1021:
don't know. Is it reliable? Obviously not. This is the emperor's new clothes syndrome, as the emperor realizes that he's not covered, so he grasps at anything that will cover his deficiencies. You helped ditch JWASM and don't have the fibre to be consistent. --
785:
4) proof that you're actually versed in the subject matter and are actually qualified to make such a judgment call and if so show that you have no bias (i.e. don't want a JWasm article because it is highly MASM compatible and you don't like
608:
While JWASM is alive and in use, Open Watcom
Assembler is a fossil, but the Wiki politicians have assured that it's the fossil without user-base that is preferable to the living, and thus in the relevant circles notable, JWASM. --
949:. Unless otherwise stated there, all content should be assumed to be written by him. You're free to sue him for copyright infringement if you believe otherwise. Until then, we will assume the citation is correctly attributed.
343:
is familiar with. His optimisation manual is both famous and appropriate to an article on x86 assembler optimisation but has no place in propping up a dead assembler that is no longer in use. Mention != reference or citation.
984:. Can you?? You can concoct any justification you like to support this clunker of an article. And why would you think of sueing someone for an unattributed blurb?? That's about as sensible as keeping this fossil article. --
383:, so you shouldn't be trying to have this article changed. That WASM is "dead" (according to you) is irrelevant, as Knowledge (XXG) is an encyclopedia, not a repository of software in current use. See also the article on
813:
3) Due to the fact that non-trivial third-party material could (not) be located that was published by people or organisations that are usually considered authoritative on those subjects and are independent of the
711:
is all that decides whether an article exists, not your personal opinions. Specific issues were discussed in previous deletion discussion that I have already linked to. Nothing is set in stone and you can file a
866:
Compiler optimization may require knowledge of assembly language but it isn't the same as being an assembly language developer. I've done quite a lot of actual x86 assembly language development including BIOS
720:
is not a valid argument here. If you're that concerned about the article being maintained, then actually maintain it, rather than ranting disruptively. The only outcome of the latter will be your banning.
605:
Now that they have assured the survival of this vestigial article, those people who made sure it stayed will never be back to add anything to it to give it any real content or credibility.
283:
Fog doesn't supply any new information about WASM. It only seems to be retained here through perverseness. It is not a source for WASM, which is the only relevant point for citing it. --
502:
for such matters he is being perfectly compliant. He has not edited the article space at all, and has only participated in the talk page for the article, which COI editors are actually
625:
31:
789:
The fact that the template for x86 assemblers has nine assemblers listed and four of those are obscure indicates that you either don't understand the subject or have a personal bias.
484:
Korath, you would be more than welcome to add independent reference and review to the list I have posted in the deletion topic for this page instead of just your statement.
462:
Do you have a different source that you would prefer to cite instead in order to substantiate our statement that WASM is "included as part of the Watcom C/C++ compiler"? —
349:
appropriate technical expertise to properly justify the notability of WASM along with independent 3rd party reference material that supports the claims of notability.
432:
Pcap, you should forget trying to attack me personally and concentrate on the shortcoming of the reference material. The
Leiterman reference is a single sentence "
1122:
147:
153:
776:
1) make a real claim which refutes any of the reasons stated for the notability of JWasm that an Intel x86 assembly language programmer would agree with.
498:
I just wanted to post here in defense of Hutch48. While it is completely reasonable to claim that he has a conflict of interest with this topic, per the
629:
123:
1117:
567:
106:
86:
790:
747:
It's easier to read the final result in the discussion than wind through the problems of mild dyslexia manifested in editing errors.
206:
188:
1094:
723:(Also try not to make so many separate edits, it's very difficult to see what's going on. "Show preview" is there for a reason).
1127:
1046:
1010:
970:
834:
734:
646:
387:
for instance, where the "dead" software is far more famous than the "live" fork, CenterIM. Back on topic, Fog's book, although
61:
853:
from a purely technical perspective JWasm is superior to these other assemblers so if they have article then so should it.
810:
2) Because significant coverage of them in reliable secondary sources could be found, or no-one disputed that they could.
717:
591:
537:
414:
302:
273:
713:
633:
27:
817:
4) I have a masters-level degree in the subject and have had peer-reviewed papers published on compiler optimisation.
897:
article. When all the non-assembly language programmers decided to delete JWASM, I removed it from the template. --
820:
5) The template for x86 assemblers was created and maintained by DocktorSpin, not me. Direct your accusations there.
925:. It's just some unsourced stuff taken off internet by someone who wanted justify keeping this fossil article. --
894:
392:
67:
588:
571:
534:
411:
299:
270:
260:
233:
Leiterman says: "I do not use it these days, but there is also the Watcom C/C++ with their WASM Assembler."
1090:
794:
708:
563:
49:
1098:
119:
881:
paste of the MASM article but if it had information specifically describing it then what is the problem ?
122:
on Knowledge (XXG). If you would like to participate, please visit the project page, where you can join
1087:
This really raises portability issues when compiling code that is perfectly legal under MASM or TASM.
489:
445:
362:
980:
You can assume whatever you like, but it certainly won't be reliable. I can't find the WASM blurb at
20:
1042:
1006:
966:
830:
730:
642:
485:
441:
358:
779:
2) make a real claim stating why several other obscure assemblers are notable while JWasm is not.
407:
256:
203:
185:
503:
467:
953:
922:
584:
530:
499:
388:
380:
1057:
1022:
985:
926:
898:
807:
1) Because significant coverage of JWasm in reliable secondary sources could not be found.
755:
692:
658:
610:
520:
313:
284:
269:
Agner describes both WASM and JWASM in an encyclopedic manner. Exactly what we need here.
240:
957:
434:
I do not use it these days, but there is also the Watcom C/C++ with their WASM Assembler.
399:
395:
230:
Welschenbach simply says: "They can be assembled using Microsoft MASM .. or Watcom WASM"
217:
1037:
1001:
961:
825:
725:
637:
255:
I restored the Leiterman reference, placing it inline to the statement it supports. --
1111:
921:
seen as a reliable 3rd party source, so it should be removed as it doesn't adhere to
750:
You make a lovely content writing recruiter for Knowledge (XXG): "If you don't like (
1102:
1066:
1051:
1031:
1015:
994:
975:
935:
907:
839:
798:
764:
739:
701:
667:
651:
619:
596:
575:
542:
525:
493:
471:
463:
449:
419:
366:
322:
312:
So the Open Watcom Assembler article is there to mention JWASM? Makes sense. --
307:
293:
278:
264:
249:
298:
He provides information about the JWASM fork; that's what the citation is for.
98:
80:
508:
175:
I have removed these references which are not serious information about WASM:
384:
115:
683:
111:
941:
The entire website is owned by Mr Hyde, as can be seen by the fact that
379:
As the developer of a competing assembler (package) you have an obvious
981:
946:
782:
3) do these in your own words without mindlessly quoting rules.
506:. His participation at this talk page is certainly welcome. --
43:
15:
942:
180:
Leiterman, James (2005). "MASM vs. NASM vs. TASM vs. WASM".
626:
Knowledge (XXG):Articles for deletion/Open Watcom Assembler
391:, does have a significant number of citations in academia
773:
Blah blah blah, can either of you two little WikiDrones™
410:
stance on multiple Knowledge (XXG) pages. Thank you,
236:
Agner Fog also says nothing instructive about WASM.
110:, a collaborative effort to improve the coverage of
152:This article has not yet received a rating on the
1056:No response would have been more meaningful. --
1000:the fuss you kicked up during JWASM's deletion.
182:32/64-bit 80x86 assembly language architecture
8:
630:Knowledge (XXG):Articles for deletion/JWASM
219:Optimizing subroutines in assembly language
1088:
707:If you don't like our rules then go away.
75:
47:
171:Fake references for Open Watcom Assembler
716:if you think the situation has changed.
684:http://www.openwatcom.com/index.php/Wasm
30:on 2 February 2010 (UTC). The result of
77:
952:Sources are not supposed to adhere to
1123:Unknown-importance Computing articles
132:Knowledge (XXG):WikiProject Computing
7:
1083:WASM does not support RECORD keyword
184:. Wordware Publishing, Inc. p. 481.
104:This article is within the scope of
66:It is of interest to the following
916:Reference ascribed to Randall Hyde
14:
982:http://homepage.mac.com/randyhyde
947:http://homepage.mac.com/randyhyde
97:
79:
48:
19:
634:Knowledge (XXG):Deletion review
26:This article was nominated for
624:If you dispute the outcome of
198:Welschenbach, Michael (2005).
135:Template:WikiProject Computing
1:
1118:Stub-Class Computing articles
1067:22:36, 17 February 2010 (UTC)
1052:22:00, 17 February 2010 (UTC)
1032:21:54, 17 February 2010 (UTC)
1016:14:00, 17 February 2010 (UTC)
995:23:32, 16 February 2010 (UTC)
976:13:34, 16 February 2010 (UTC)
936:01:17, 16 February 2010 (UTC)
908:22:20, 17 February 2010 (UTC)
840:19:09, 17 February 2010 (UTC)
799:16:31, 17 February 2010 (UTC)
765:22:34, 17 February 2010 (UTC)
740:13:53, 17 February 2010 (UTC)
702:07:47, 17 February 2010 (UTC)
668:23:35, 16 February 2010 (UTC)
652:13:37, 16 February 2010 (UTC)
620:02:10, 15 February 2010 (UTC)
335:Reference and citation errors
126:and see a list of open tasks.
956:, the relevant guideline is
597:10:18, 3 February 2010 (UTC)
576:05:48, 3 February 2010 (UTC)
543:22:15, 2 February 2010 (UTC)
526:17:43, 2 February 2010 (UTC)
494:10:15, 2 February 2010 (UTC)
472:08:49, 2 February 2010 (UTC)
450:08:39, 2 February 2010 (UTC)
420:08:16, 2 February 2010 (UTC)
367:07:29, 2 February 2010 (UTC)
323:05:34, 2 February 2010 (UTC)
308:05:11, 2 February 2010 (UTC)
294:05:03, 2 February 2010 (UTC)
279:00:55, 2 February 2010 (UTC)
265:00:19, 2 February 2010 (UTC)
250:00:09, 2 February 2010 (UTC)
533:I took the article to AfD.
1144:
1103:14:19, 19 March 2016 (UTC)
1036:Pot? Have you met kettle?
154:project's importance scale
943:http://webster.cs.ucr.edu
200:Cryptography in C and C++
151:
92:
74:
895:Comparison of assemblers
225:(2009-09-26 ed.), p. 13
1128:All Computing articles
402:, and that would help
120:information technology
56:This article is rated
107:WikiProject Computing
60:on Knowledge (XXG)'s
752:my interpretation of
824:further responses.
718:WP:OTHERSTUFFEXISTS
216:Fog, Agner (2009),
714:WP:Deletion review
408:passive aggressive
202:. Apress. p. 418.
138:Computing articles
62:content assessment
1105:
1093:comment added by
1050:
1014:
974:
838:
738:
724:
650:
594:
566:comment added by
540:
417:
305:
276:
168:
167:
164:
163:
160:
159:
42:
41:
1135:
1063:
1062:
1040:
1028:
1027:
1004:
991:
990:
964:
932:
931:
904:
903:
828:
761:
760:
728:
722:
698:
697:
664:
663:
640:
616:
615:
602:voted to remove.
592:
578:
538:
523:
517:
514:
511:
504:encouraged to do
415:
319:
318:
303:
290:
289:
274:
246:
245:
226:
224:
212:
194:
140:
139:
136:
133:
130:
101:
94:
93:
83:
76:
59:
53:
52:
44:
23:
16:
1143:
1142:
1138:
1137:
1136:
1134:
1133:
1132:
1108:
1107:
1085:
1060:
1059:
1025:
1024:
988:
987:
929:
928:
918:
901:
900:
758:
757:
695:
694:
661:
660:
613:
612:
561:
557:
521:
515:
512:
509:
406:more than your
337:
316:
315:
287:
286:
243:
242:
222:
215:
209:
197:
191:
179:
173:
137:
134:
131:
128:
127:
57:
12:
11:
5:
1141:
1139:
1131:
1130:
1125:
1120:
1110:
1109:
1084:
1081:
1080:
1079:
1078:
1077:
1076:
1075:
1074:
1073:
1072:
1071:
1070:
1069:
950:
917:
914:
913:
912:
911:
910:
887:
886:
885:
884:
883:
882:
873:
872:
871:
870:
869:
868:
859:
858:
857:
856:
855:
854:
845:
844:
843:
842:
821:
818:
815:
811:
808:
802:
801:
787:
783:
780:
777:
774:
770:
769:
768:
767:
748:
705:
704:
679:
678:
677:
676:
675:
674:
673:
672:
671:
670:
606:
603:
556:
553:
552:
551:
550:
549:
548:
547:
546:
545:
479:
478:
477:
476:
475:
474:
455:
454:
453:
452:
438:
437:
427:
426:
425:
424:
423:
422:
394:, making it a
372:
371:
370:
369:
353:
352:
351:
350:
346:
345:
344:
336:
333:
332:
331:
330:
329:
328:
327:
326:
325:
267:
228:
227:
213:
207:
195:
189:
172:
169:
166:
165:
162:
161:
158:
157:
150:
144:
143:
141:
124:the discussion
102:
90:
89:
84:
72:
71:
65:
54:
40:
39:
32:the discussion
24:
13:
10:
9:
6:
4:
3:
2:
1140:
1129:
1126:
1124:
1121:
1119:
1116:
1115:
1113:
1106:
1104:
1100:
1096:
1092:
1082:
1068:
1065:
1064:
1055:
1054:
1053:
1048:
1044:
1039:
1035:
1034:
1033:
1030:
1029:
1019:
1018:
1017:
1012:
1008:
1003:
998:
997:
996:
993:
992:
983:
979:
978:
977:
972:
968:
963:
959:
955:
951:
948:
945:redirects to
944:
940:
939:
938:
937:
934:
933:
924:
915:
909:
906:
905:
896:
891:
890:
889:
888:
879:
878:
877:
876:
875:
874:
865:
864:
863:
862:
861:
860:
851:
850:
849:
848:
847:
846:
841:
836:
832:
827:
822:
819:
816:
812:
809:
806:
805:
804:
803:
800:
796:
792:
788:
784:
781:
778:
775:
772:
771:
766:
763:
762:
753:
749:
746:
745:
744:
743:
742:
741:
736:
732:
727:
719:
715:
710:
709:WP:Notability
703:
700:
699:
689:
688:
687:
685:
669:
666:
665:
655:
654:
653:
648:
644:
639:
635:
632:, take it to
631:
627:
623:
622:
621:
618:
617:
607:
604:
600:
599:
598:
595:
590:
586:
583:
582:
581:
580:
579:
577:
573:
569:
565:
554:
544:
541:
536:
532:
529:
528:
527:
524:
519:
518:
505:
501:
497:
496:
495:
491:
487:
483:
482:
481:
480:
473:
469:
465:
461:
460:
459:
458:
457:
456:
451:
447:
443:
439:
435:
431:
430:
429:
428:
421:
418:
413:
409:
405:
401:
397:
393:
390:
386:
382:
378:
377:
376:
375:
374:
373:
368:
364:
360:
357:
356:
355:
354:
347:
341:
340:
339:
338:
334:
324:
321:
320:
311:
310:
309:
306:
301:
297:
296:
295:
292:
291:
282:
281:
280:
277:
272:
268:
266:
262:
258:
257:SarekOfVulcan
254:
253:
252:
251:
248:
247:
237:
234:
231:
221:
220:
214:
210:
208:9781590595022
205:
201:
196:
192:
190:9781598220025
187:
183:
178:
177:
176:
170:
155:
149:
146:
145:
142:
125:
121:
117:
113:
109:
108:
103:
100:
96:
95:
91:
88:
85:
82:
78:
73:
69:
63:
55:
51:
46:
45:
37:
33:
29:
25:
22:
18:
17:
1089:— Preceding
1086:
1058:
1023:
986:
927:
919:
899:
867:development.
756:
751:
706:
693:
680:
659:
611:
568:99.48.51.132
558:
507:
433:
403:
314:
285:
241:
238:
235:
232:
229:
218:
199:
181:
174:
105:
68:WikiProjects
35:
791:99.33.29.61
562:—Preceding
1112:Categories
1095:83.6.61.24
786:Microsoft)
555:Notability
531:That's why
500:guidelines
58:Stub-class
1038:OrangeDog
1002:OrangeDog
962:OrangeDog
826:OrangeDog
726:OrangeDog
638:OrangeDog
440:Regards.
385:CenterICQ
129:Computing
116:computing
112:computers
87:Computing
1091:unsigned
814:subject.
564:unsigned
28:deletion
486:Hutch48
442:Hutch48
359:Hutch48
954:WP:GNG
923:WP:GNG
585:WP:GNG
464:Korath
389:WP:SPS
381:WP:COI
118:, and
64:scale.
958:WP:RS
400:WP:RS
396:WP:RS
223:(PDF)
1099:talk
1061:spin
1026:spin
989:spin
930:spin
902:spin
795:talk
759:spin
696:spin
662:spin
614:spin
593:ping
589:Pcap
572:talk
539:ping
535:Pcap
490:talk
468:Talk
446:talk
416:ping
412:Pcap
363:talk
317:spin
304:ping
300:Pcap
288:spin
275:ping
271:Pcap
261:talk
244:spin
204:ISBN
186:ISBN
36:keep
34:was
628:or
404:far
239:--
148:???
1114::
1101:)
1045:•
1009:•
969:•
960:.
833:•
797:)
733:•
645:•
636:.
587:.
574:)
513:am
510:At
492:)
470:)
448:)
365:)
263:)
114:,
1097:(
1049:)
1047:ε
1043:Ď„
1041:(
1013:)
1011:ε
1007:Ď„
1005:(
973:)
971:ε
967:Ď„
965:(
837:)
835:ε
831:Ď„
829:(
793:(
737:)
735:ε
731:Ď„
729:(
682:(
649:)
647:ε
643:Ď„
641:(
570:(
522:é
516:a
488:(
466:(
444:(
361:(
259:(
211:.
193:.
156:.
70::
38:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
