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

Groups > comp.lang.forth > #40308 > unrolled thread

Release Win32Forth AVS virus report testing code declaration

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

Contents

  Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-05 04:29 -0700
    Re: Release Win32Forth AVS virus report testing code declaration "Alex McDonald" <blog@rivadpm.com> - 2015-07-05 16:06 +0100
      Re: Release Win32Forth AVS virus report testing code declaration Hannu Vuolasaho <vuokkosetae@gmail.com> - 2015-07-05 20:01 +0300
        Re: Release Win32Forth AVS virus report testing code declaration "Alex McDonald" <blog@rivadpm.com> - 2015-07-05 22:23 +0100
      Re: Release Win32Forth AVS virus report testing code declaration bettilyona@gmail.com - 2015-07-06 08:02 -0700
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-05 15:46 -0700
      Re: Release Win32Forth AVS virus report testing code declaration "Alex McDonald" <blog@rivadpm.com> - 2015-07-06 08:17 +0100
        Re: Release Win32Forth AVS virus report testing code declaration Jan Coombs <Jan-54 <jenfhaomndgfwutc@murmic.plus.com>> - 2015-07-06 11:39 +0100
          Re: Release Win32Forth AVS virus report testing code declaration "Alex McDonald" <blog@rivadpm.com> - 2015-07-06 15:17 +0100
        Re: Release Win32Forth AVS virus report testing code declaration "Alex McDonald" <blog@rivadpm.com> - 2015-07-06 20:54 +0100
          Re: Release Win32Forth AVS virus report testing code declaration "Elizabeth D. Rather" <erather@forth.com> - 2015-07-06 12:14 -1000
          Re: Release Win32Forth AVS virus report testing code declaration hughaguilar96@gmail.com - 2015-07-06 18:56 -0700
      Re: Release Win32Forth AVS virus report testing code declaration josv@planet.nl - 2015-07-06 03:07 -0700
        Re: Release Win32Forth AVS virus report testing code declaration "Alex McDonald" <blog@rivadpm.com> - 2015-07-06 16:13 +0100
      Re: Release Win32Forth AVS virus report testing code declaration rickman <gnuarm@gmail.com> - 2015-07-06 08:31 -0400
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-06 03:14 -0700
      Re: Release Win32Forth AVS virus report testing code declaration Mark Wills <markwills1970@gmail.com> - 2015-07-06 03:30 -0700
      Re: Release Win32Forth AVS virus report testing code declaration "Alex McDonald" <blog@rivadpm.com> - 2015-07-06 15:21 +0100
      Re: Release Win32Forth AVS virus report testing code declaration rickman <gnuarm@gmail.com> - 2015-07-06 12:29 -0400
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-06 03:21 -0700
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-06 16:25 -0700
      Re: Release Win32Forth AVS virus report testing code declaration "Alex McDonald" <blog@rivadpm.com> - 2015-07-07 07:59 +0100
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-06 21:41 -0700
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-07 02:43 -0700
      Re: Release Win32Forth AVS virus report testing code declaration Mark Wills <markwills1970@gmail.com> - 2015-07-07 03:10 -0700
        Re: Release Win32Forth AVS virus report testing code declaration Mark Wills <markwills1970@gmail.com> - 2015-07-07 03:17 -0700
          Re: Release Win32Forth AVS virus report testing code declaration mhx@iae.nl - 2015-07-07 11:31 -0700
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-07 03:18 -0700
      Re: Release Win32Forth AVS virus report testing code declaration rickman <gnuarm@gmail.com> - 2015-07-07 08:38 -0400
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-07 03:25 -0700
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-07 21:59 -0700
      Re: Release Win32Forth AVS virus report testing code declaration "Alex McDonald" <blog@rivadpm.com> - 2015-07-08 13:04 +0100
        Re: Release Win32Forth AVS virus report testing code declaration josv@planet.nl - 2015-07-08 14:39 -0700
        Re: Release Win32Forth AVS virus report testing code declaration hughaguilar96@gmail.com - 2015-07-08 21:30 -0700
          Re: Release Win32Forth AVS virus report testing code declaration rickman <gnuarm@gmail.com> - 2015-07-09 01:20 -0400
            Re: Release Win32Forth AVS virus report testing code declaration josv@planet.nl - 2015-07-09 04:19 -0700
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-08 15:50 -0700
      Re: Release Win32Forth AVS virus report testing code declaration rickman <gnuarm@gmail.com> - 2015-07-08 19:39 -0400
    Re: Release Win32Forth AVS virus report testing code declaration josv@planet.nl - 2015-07-09 04:17 -0700
      Re: Release Win32Forth AVS virus report testing code declaration josv@planet.nl - 2015-07-09 04:27 -0700
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-09 05:56 -0700
      Re: Release Win32Forth AVS virus report testing code declaration josv@planet.nl - 2015-07-09 09:48 -0700
        Re: Release Win32Forth AVS virus report testing code declaration rickman <gnuarm@gmail.com> - 2015-07-09 13:00 -0400
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-09 15:39 -0700
      Re: Release Win32Forth AVS virus report testing code declaration Julian Fondren <julian.fondren@gmail.com> - 2015-07-09 19:05 -0700
    Re: Release Win32Forth AVS virus report testing code declaration Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-10 02:26 -0700

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

#40308 — Release Win32Forth AVS virus report testing code declaration

To all readers,

I will do what I said: no reply, no comment from me to any dirty reader here.

After 5 years, a code monkey is still being a code monkey. He found his virus report. Until 5 years past, he is still can do the same thing "just complained" only, what can I say to such a monkey? Answer is "No reply, no comment forever". Unfortunately, face to such a monkey; make me have no interesting to post my total testing code here.

Everybody has the same "AVS virus report" problem while he installed Win32Forth into W7, me too. It means this is not happened recently. So I don't have to emphasize when this problem was happened to me and had been discussed in my FORTH community already. But I do what I should to do, never to do what a monkey used to do.

Monkeys must to learn "how to learn forth?" Otherwise, monkeys can only just g-g-footh all his life long. I am always hear this monkey's g-g- sound here.

If anybody is still have the interesting in my testing code, you are welcome to contact me directly and have my little testing code file free. Monkeys are prohibited! 

This Win32Forth AVS virus topic is just coming out again here few days ago. Owing to this monkey, I am very sorry; I will not post these codes here or that thread there.

I am feeling that most FORTH novice didn't used to practice programming by protocol phenomena (or means a few fixed procedures get together simultaneously), and always wish to implement out a system problem by a few FORTH words, for example discussing about Matrices structure design. My code may show you these phenomena and help a little.

Even though this code is writing in Win64 assembly, total procedures and contents are sorted out from Win32Forth for testing, can show you a delicate procedure at least. Testing result for the moment may tell you what the Win64 OS can or can not let general FORTH system do the keyboard I/O on the command console via this kind of function calling from kernel.dll only? It may help something to create a Win64 public domain FORTH. 

This file can be implementing out by just type in

>FASM ex.asm

Then generate an executable file ex.exe in less than 0.5 sec. You can execute it in command console directly and see the result. We don't have so many typical Win64 assembly demo code source now. Here is mine one. You may don't have to execute it and just read it for my posting reference.

After I post this declaration out, I will tidy up my code for e-mail sending tomorrow. It may still keep a few Chinese explanations inside for Chinese reader. Please don't contact me if without sincerity. How to contact me? Please refer to my personal website.

http://forthfortnight.blogspot.co.nz/

Please don't reply anything here. I will not reply any words here.

Ching

[toc] | [next] | [standalone]

#40315

on 05/07/2015 12:29:13, Ching-Tang Tseng wrote:
> To all readers,
> 
> I will do what I said: no reply, no comment from me to any dirty
> reader her e.
> 
> After 5 years, a code monkey is still being a code monkey. He found
> his vir us report. Until 5 years past, he is still can do the same
> thing "just comp lained" only, what can I say to such a monkey? Answer
> is "No reply, no comm ent forever". Unfortunately, face to such a
> monkey; make me have no interes ting to post my total testing code
> here.
> 

I was polite to you until you called me a "code monkey" in ths thread
earlier, but here you are repeating the insult.

As one of the authors of Win32Forth, I sometimes wish that I had a
licence that allowed me to release my code under a "anyone but these
clueless asswipes <list of names>" licence. You'd be in that <list of
names> as of today.

But there isn't such an open source licence, so you're free to use the
efforts of this "code monkey".

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

#40322

On 05.07.2015 18:06, Alex McDonald wrote:

> As one of the authors of Win32Forth, I sometimes wish that I had a
> licence that allowed me to release my code under a "anyone but these
> clueless asswipes <list of names>" licence. You'd be in that <list of
> names> as of today.
>
> But there isn't such an open source licence, so you're free to use the
> efforts of this "code monkey".
>
https://github.com/landondyer/kasm/blob/master/LICENSE

But that needs some development and add some wipes.

Best regards,
Hannu Vuolasaho

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

#40326

on 05/07/2015 18:01:09, Hannu Vuolasaho wrote:
> On 05.07.2015 18:06, Alex McDonald wrote:
> 
>> As one of the authors of Win32Forth, I sometimes wish that I had a
>> licence that allowed me to release my code under a "anyone but these
>> clueless asswipes <list of names>" licence. You'd be in that <list of
>> names> as of today.
>>
>> But there isn't such an open source licence, so you're free to use the
>> efforts of this "code monkey".
>>
> https://github.com/landondyer/kasm/blob/master/LICENSE
> 
> But that needs some development and add some wipes.
> 
> Best regards,
> Hannu Vuolasaho
> 

See clause 5 of the DFSG.
http://www.debian.org/social_contract#guidelines.

Busted ;-)

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

#40364

On Sunday, July 5, 2015 at 9:06:42 AM UTC-6, Alex McDonald wrote:
> on 05/07/2015 12:29:13, Ching-Tang Tseng wrote:
> > To all readers,
> > 
> > I will do what I said: no reply, no comment from me to any dirty
> > reader her e.
> > 
> > After 5 years, a code monkey is still being a code monkey. He found
> > his vir us report. Until 5 years past, he is still can do the same
> > thing "just comp lained" only, what can I say to such a monkey? Answer
> > is "No reply, no comm ent forever". Unfortunately, face to such a
> > monkey; make me have no interes ting to post my total testing code
> > here.
> > 
> 
> I was polite to you until you called me a "code monkey" in ths thread
> earlier, but here you are repeating the insult.
> 
> As one of the authors of Win32Forth, I sometimes wish that I had a
> licence that allowed me to release my code under a "anyone but these
> clueless asswipes <list of names>" licence. You'd be in that <list of
> names> as of today.
> 
> But there isn't such an open source licence, so you're free to use the
> efforts of this "code monkey".

Instead of "code monkey", would it be less insulting to be called a "code 500 pound gorilla with rocket launchers"?

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

#40330

To busted Alex,

No wonder, I am always feeling that some so called "as one of authors" do many bad things to Win32Forth, make it diverted into the bad condition, and expel the good contributors away, make them left and don't like to contribute anything again. After Version 4.2, there were many versions are not worth to use and to be proved had pirated code from other copyright system. I had read these kinds of discussion many times here and feel shame. A lot of Win32Forth users understand these situations. I had ever pointed it out in my article. Have my name in your dirty listing is good. It seems we should have a bad authors listing as well. Bad author's name should be public. Please don't contaminated Win32Forth with any kinds of format again. Just talk virus report only for many years, then always to frustrate others do testing to find out what function calling make it happened, this thing included. Everybody should stop to downgrade Win32Forth by the way of so called as one of authors. Nobody will think a bad author is an author. Enough is enough. I'd like to use public domain good parts only, reject all bad authors doing. Unfortunately, dirty things had been mixed in the good system already and hard to separate. No wonder just talk sustained so many years.

No reply please. Stop all talking here, this is one shame thing in Win32Forth domain not belongs to others. It is a closed door shame.

Ching

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

#40348

on 05/07/2015 23:46:27, Ching-Tang Tseng wrote:
> 
> 
> To busted Alex,
> 
> No wonder, I am always feeling that some so called "as one of authors"
> do m any bad things to Win32Forth, make it diverted into the bad
> condition, and expel the good contributors away, make them left and
> don't like to contribu te anything again. After Version 4.2, there
> were many versions are not wort h to use and to be proved had pirated
> code from other copyright system. I h ad read these kinds of
> discussion many times here and feel shame. A lot of Win32Forth users
> understand these situations. I had ever pointed it out in my article.

Please post a link to the article. Don't worry if it's in Chinese, I'm
sure I can get it translated.

> Have my name in your dirty listing is good. It seems we should have a
> bad authors listing as well. Bad author's name should be public. Ple
> ase don't contaminated Win32Forth with any kinds of format again. Just
> talk virus report only for many years, then always to frustrate others
> do testi ng to find out what function calling make it happened, this
> thing included. Everybody should stop to downgrade Win32Forth by the
> way of so called as o ne of authors. Nobody will think a bad author is
> an author. Enough is enoug h. I'd like to use public domain good parts
> only, reject all bad authors do ing. Unfortunately, dirty things had
> been mixed in the good system already and hard to separate. No wonder
> just talk sustained so many years.
> 
> No reply please. Stop all talking here, this is one shame thing in
> Win32For th domain not belongs to others. It is a closed door shame.
> 
> Ching
> 

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

#40359

On Mon, 6 Jul 2015 08:17:31 +0100
"Alex McDonald" <blog@rivadpm.com> wrote:

> Please post a link to the article. Don't worry
> if it's in Chinese, I'm sure I can get it
> translated.

Good modern dictionary, downloadable as text file:

http://www.mdbg.net/chindict/chindict.php?page=cedict

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

#40362

on 06/07/2015 11:39:07, Jan Coombs wrote:
> On Mon, 6 Jul 2015 08:17:31 +0100
> "Alex McDonald" <blog@rivadpm.com> wrote:
> 
>> Please post a link to the article. Don't worry
>> if it's in Chinese, I'm sure I can get it
>> translated.
> 
> Good modern dictionary, downloadable as text file:
> 
> http://www.mdbg.net/chindict/chindict.php?page=cedict
> 
> 
> 

Thanks. I'm sorted, since Google Translate tells me that "code monkey" is
????.

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

#40370

on 06/07/2015 08:17:31, "Alex McDonald" wrote:
> on 05/07/2015 23:46:27, Ching-Tang Tseng wrote:
>>
>>
>> To busted Alex,
>>
>> No wonder, I am always feeling that some so called "as one of authors"
>> do m any bad things to Win32Forth, make it diverted into the bad
>> condition, and expel the good contributors away, make them left and
>> don't like to contribu te anything again. After Version 4.2, there
>> were many versions are not wort h to use and to be proved had pirated
>> code from other copyright system. I h ad read these kinds of
>> discussion many times here and feel shame. A lot of Win32Forth users
>> understand these situations. I had ever pointed it out in my article.
> 
> Please post a link to the article. Don't worry if it's in Chinese, I'm
> sure I can get it translated.

I found the post here
http://forthfortnight.blogspot.co.uk/2011_12_01_archive.html, last
article.

Translated from the Chinese via Google translate, it seems to suggest
that Win32Forth v6.14 has elements of other people's copyrighted work in
it; specifically, a bug fix to FEXPM1 which Ching believes was done by
copying code from SwiftForth. And possibly other plagiarised code from
Swiftforth, although the translation is bad at this point and I could be
mistaken.

"On the future direction of the system appears, Win32Forth V6.14 for me,
only the reference value, it is the source of plagiarism swift Forth
[SwiftForth], have more true technology"

"In fact, these later versions are not outstanding achievements, but also
copied many similar swift Forth [SwiftForth] source program or other
system, since copied the wrong place and many have been accused, for
example: Recently someone attacks V6.14 New float.f program The FEXPM1,
it copied the wrong label skip position than after the original author is
very proud of the new post- flaming speechless, so I have to practice
this system feel ashamed. Borrow someone else's program development
system is no shame, do not strictly prohibited, can not be copied, do not
copy, we should respect the original and borrowed indicate the source, so
we can not do a simple courtesy, is a disgrace, it is no wonder the
system scale Disease place so much."

I can categorically state that I have never used SwiftForth, and that
I've never seen any SwiftForth source code (excepting what Elizabeth
Rather may have posted here). Other authors will, I am absolutely sure,
assert that they haven't copied SwiftForth source code either.

Hugh made his contribution in the form of a bug report (although he did
disassemble SwiftForth to provide a suggestion as to how it might be
fixed). George Hubert wrote the correction for FEXPM1 in FLOAT.F. No
reference was made to SwiftForth source code, nor the disassembly that
Hugh provided.
https://groups.google.com/forum/#!topic/comp.lang.forth/jVCvbyufTEQ

I take accusations like this seriously, and I'll deal with them if they
are brought to my attention. If anyone can make out any other accusations
in the article, or has any evidence that would cause concern about the
original nature of Win32Forth code contributed by me or any other person
since we picked up Win32Forth 4.2, please let me know here.

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

#40374

On 7/6/15 9:54 AM, Alex McDonald wrote:
> Hugh made his contribution in the form of a bug report (although he did
> disassemble SwiftForth to provide a suggestion as to how it might be
> fixed). George Hubert wrote the correction for FEXPM1 in FLOAT.F. No
> reference was made to SwiftForth source code, nor the disassembly that
> Hugh provided.
> https://groups.google.com/forum/#!topic/comp.lang.forth/jVCvbyufTEQ

In 2011 Hugh reported bugs in a SwiftForth v.2, which would have dated 
from prior to 2006 (when 3.0 was distributed). As in the VFX case 
currently under discussion, some of his bug reports were misunderstandings.

Cheers,
Elizabeth

-- 
==================================================
Elizabeth D. Rather   (US & Canada)   800-55-FORTH
FORTH Inc.                         +1 310.999.6784
5959 West Century Blvd. Suite 700
Los Angeles, CA 90045
http://www.forth.com

"Forth-based products and Services for real-time
applications since 1973."
==================================================

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

#40377

On Monday, July 6, 2015 at 12:54:08 PM UTC-7, Alex McDonald wrote:
> Hugh made his contribution in the form of a bug report (although he did
> disassemble SwiftForth to provide a suggestion as to how it might be
> fixed). George Hubert wrote the correction for FEXPM1 in FLOAT.F. No
> reference was made to SwiftForth source code, nor the disassembly that
> Hugh provided.
> https://groups.google.com/forum/#!topic/comp.lang.forth/jVCvbyufTEQ

Alex McDonald purposely misrepresents things.

I didn't post the SwiftForth version of FEXPM1 as a suggestion as to how FEXPM1 might be fixed --- I posted the SwiftForth version of FEXPM1 as a joke, because it was completely screwed up too --- I think this should be obvious to anybody who reads that thread.

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

#40355

> this is one shame thing in Win32Forth domain not belongs to others.
Win32Forth belongs to nobody.
IMO Win32Forth is still a nice free system in which a programs can be developed in a fast way.

Jos

On 6 July 2015 00:46:27 UTC+2 wrote Ching-Tang wrote:
> To busted Alex,
> 
> No wonder, I am always feeling that some so called "as one of authors" do many bad things to Win32Forth, make it diverted into the bad condition, and expel the good contributors away, make them left and don't like to contribute anything again. After Version 4.2, there were many versions are not worth to use and to be proved had pirated code from other copyright system. I had read these kinds of discussion many times here and feel shame. A lot of Win32Forth users understand these situations. I had ever pointed it out in my article. Have my name in your dirty listing is good. It seems we should have a bad authors listing as well. Bad author's name should be public. Please don't contaminated Win32Forth with any kinds of format again. Just talk virus report only for many years, then always to frustrate others do testing to find out what function calling make it happened, this thing included. Everybody should stop to downgrade Win32Forth by the way of so called as one of authors. Nobody will think a bad author is an author. Enough is enough. I'd like to use public domain good parts only, reject all bad authors doing. Unfortunately, dirty things had been mixed in the good system already and hard to separate. No wonder just talk sustained so many years.
> 
> No reply please. Stop all talking here, this is one shame thing in Win32Forth domain not belongs to others. It is a closed door shame.
> 
> Ching

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

#40365

on 06/07/2015 11:07:52,  wrote:
>> this is one shame thing in Win32Forth domain not belongs to others.
> Win32Forth belongs to nobody.
> IMO Win32Forth is still a nice free system in which a programs can be
> devel oped in a fast way.
> 
> Jos

Yes, very much so. For Windows users, it's a fairly painless introduction
to Forth. It is also almost all public domain code.

The history is quite interesting, and the contributors list particularly
so, since you and I worked with many others in 2004 onwards after Tom
Zimmer's interests took him elsewhere (mainly Java). Win32Forth was an
ITC developed by Tom, Andrew McEwan, Andy Korsack (and Jim Schneider who
did the original assembler). All of it was public domain, except for the
assembler which was GPLv2. I managed to get Jim to re-release it under a
retrospective LGPL in 2003, since it was a bit problematic just having it
released under the GPL.

At one point we had Robert Dudley Ackerman, Ezra Boyce, Dirk Busch,
Thomas Dixon, Camille Doiteau, Brad Eckert (posts here), Bruno Gauthier,
George Hubert (posts here occasionally), Alex McDonald (that's me), Rod
Oakford (posts here occasionally), Andrew Stephenson, Jos van de Ven
(that's you) and others...

Ron Aaron (still posts here, inventor of 8th) ran a CVS for us for a
while, and there was a guy called John A Peters, whom I think ran some
kind of electrical engineering business around Sunnyvale in CA, who ran a
mailing list for us in the early days. I met him once at a Forth Day in
(iirc) Santa Clara, along with Dr Ting, Jeff Fox amd Chuck Moore. Rainbow
Sally (whose real name I never did get) and I hacked all the C code out
of Win32Forth and made it a 100% Forth only system.

A few years back, my interests led me to develop an ANS compliant Forth
based on Win32Forth, but quite different and experimental in how it
compiles. It's never been released into the wild, but I may be tempted
one of these days. I gave up being one of the major contributors and
maintainer of Win32Forth (around the release of 6.14 in 2010) as a
result.

The current versions of Win32Forth are all still PD, excepting the
assembler which is LGPL. That PD is important, since it gives anyone the
ability to take the code and use it as they see fit. Win32Forth (minus
486ASM.F and a couple of other supporting files as they're LGPL) belongs
to nobody and everybody. All of which (as I pointed out elsewhere) gives
Ching carte blanche to do what he wants with it. He's as free as anyone
else to use or abuse it.

Hopefully this also highlights what a steaming load of crap it is that
Ching sees fit to post about me.

> 
> On 6 July 2015 00:46:27 UTC+2 wrote Ching-Tang wrote:
>> To busted Alex,
>>
>> No wonder, I am always feeling that some so called "as one of authors" do
> many bad things to Win32Forth, make it diverted into the bad
> condition, an d expel the good contributors away, make them left and
> don't like to contri bute anything again. After Version 4.2, there
> were many versions are not wo rth to use and to be proved had pirated
> code from other copyright system. I had read these kinds of discussion
> many times here and feel shame. A lot o f Win32Forth users understand
> these situations. I had ever pointed it out i n my article. Have my
> name in your dirty listing is good. It seems we shoul d have a bad
> authors listing as well. Bad author's name should be public. P lease
> don't contaminated Win32Forth with any kinds of format again. Just ta
> lk virus report only for many years, then always to frustrate others
> do tes ting to find out what function calling make it happened, this
> thing include d. Everybody should stop to downgrade Win32Forth by the
> way of so called as one of authors. Nobody will think a bad author is
> an author. Enough is eno ugh. I'd like to use public domain good parts
> only, reject all bad authors doing. Unfortunately, dirty things had
> been mixed in the good system alread y and hard to separate. No wonder
> > just talk sustained so many years.
>>
> > just talk sustained so many years.
>> No reply please. Stop all talking here, this is one shame thing in Win32F
> just talk sustained so many years. orth domain not belongs to others.
> > It is a closed door shame.
>>
> > It is a closed door shame.
>> Ching
> It is a closed door shame.
> 
> 

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

#40361

On 7/5/2015 6:46 PM, Ching-Tang Tseng wrote:
>
>
> To busted Alex,
>
> No wonder, I am always feeling that some so called "as one of authors" do many bad things to Win32Forth, make it diverted into the bad condition, and expel the good contributors away, make them left and don't like to contribute anything again. After Version 4.2, there were many versions are not worth to use and to be proved had pirated code from other copyright system. I had read these kinds of discussion many times here and feel shame. A lot of Win32Forth users understand these situations. I had ever pointed it out in my article. Have my name in your dirty listing is good. It seems we should have a bad authors listing as well. Bad author's name should be public. Please don't contaminated Win32Forth with any kinds of format again. Just talk virus report only for many years, then always to frustrate others do testing to find out what function calling make it happened, this thing included. Everybody should stop to downgrade Win32Forth by the way of so called as one of authors. Nobod
y will think a bad author is an author. Enough is enough. I'd like to use public domain good parts only, reject all bad authors doing. Unfortunately, dirty things had been mixed in the good system already and hard to separate. No wonder just talk sustained so many years.
>
> No reply please. Stop all talking here, this is one shame thing in Win32Forth domain not belongs to others. It is a closed door shame.
>
> Ching

Amazing.

-- 

Rick

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

#40356

Alex,

I have written a FORTH book base on whole Win32Forth system. Your name has never been found in the acknowledgement listing. Owing to you are really a shameless liar, occupied Win32Forth such a good creation from Tom Zimmer and Andrew Mckewan, and destroyed this good system after version 4.2 by way of so called "AS" one of authors, You'd better don't read my article even Chinese.

I guess you are at most like to use *.dll to call others function only. Especially I have no interesting in this code monkey style not real FORTH programming method.

How many times do I have to say it to you? Don't reply. Your bad name exists here already. Do real positive contributions to Win32Forth, make public confirm you, and then you may improve your reputation. If you can reach this point, you may to be a good friend to me in the future, but not now.

If you are really want to learn the real FORTH spirit and about that article, try to ask other Chinese to help you. Writers hate to give reading guide to anybody. Parts of my articles have been over there for almost 7 years. All Chinese FORTH users know it. 

This time, I am control my temper and polite enough. Can we really finish all talking now? Don't bother me or my friend Hugh again. I need time to design FORTH program. Please let me alone.

Ching

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

#40358

On Monday, 6 July 2015 11:14:40 UTC+1, Ching-Tang Tseng  wrote:
> Alex,
> 
> I have written a FORTH book base on whole Win32Forth system. Your name has never been found in the acknowledgement listing. Owing to you are really a shameless liar, occupied Win32Forth such a good creation from Tom Zimmer and Andrew Mckewan, and destroyed this good system after version 4.2 by way of so called "AS" one of authors, You'd better don't read my article even Chinese.
> 
> I guess you are at most like to use *.dll to call others function only. Especially I have no interesting in this code monkey style not real FORTH programming method.
> 
> How many times do I have to say it to you? Don't reply. Your bad name exists here already. Do real positive contributions to Win32Forth, make public confirm you, and then you may improve your reputation. If you can reach this point, you may to be a good friend to me in the future, but not now.
> 
> If you are really want to learn the real FORTH spirit and about that article, try to ask other Chinese to help you. Writers hate to give reading guide to anybody. Parts of my articles have been over there for almost 7 years. All Chinese FORTH users know it. 
> 
> This time, I am control my temper and polite enough. Can we really finish all talking now? Don't bother me or my friend Hugh again. I need time to design FORTH program. Please let me alone.
> 
> Ching

It's really not viable to have a Windows based Forth system that does
*not* access the host facilities via DLLs. It sounds like Win32Forth
is not for you. You might be better with a stand-alone Forth, or a Forth
running on top of a lighter OS. Even Linux based Forths need to 
interface with the OS for things like file access. You can't avoid it.
It's not really fair to blame Alex for interfacing to Windows via
the Windows API. That's what it's there for!

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

#40363

on 06/07/2015 11:14:38, Ching-Tang Tseng wrote:
> Alex,
> 
> I have written a FORTH book base on whole Win32Forth system. 

Is it online?

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

#40366

On 7/6/2015 6:14 AM, Ching-Tang Tseng wrote:
> Alex,
>
> I have written a FORTH book base on whole Win32Forth system. Your name has never been found in the acknowledgement listing. Owing to you are really a shameless liar, occupied Win32Forth such a good creation from Tom Zimmer and Andrew Mckewan, and destroyed this good system after version 4.2 by way of so called "AS" one of authors, You'd better don't read my article even Chinese.
>
> I guess you are at most like to use *.dll to call others function only. Especially I have no interesting in this code monkey style not real FORTH programming method.
>
> How many times do I have to say it to you? Don't reply. Your bad name exists here already. Do real positive contributions to Win32Forth, make public confirm you, and then you may improve your reputation. If you can reach this point, you may to be a good friend to me in the future, but not now.
>
> If you are really want to learn the real FORTH spirit and about that article, try to ask other Chinese to help you. Writers hate to give reading guide to anybody. Parts of my articles have been over there for almost 7 years. All Chinese FORTH users know it.
>
> This time, I am control my temper and polite enough. Can we really finish all talking now? Don't bother me or my friend Hugh again. I need time to design FORTH program. Please let me alone.
>
> Ching

You have amazing gall.  I can't imagine why anyone in this group would 
reply to anything you write.  I certainly will be ignoring you.  I'm 
hoping others will do the same and end this pointless thread.

BTW, I do see why you feel like Hugh is a friend.  You two have a lot in 
common.

-- 

Rick

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

#40357

To Jos,

agree!

Ching

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

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

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

csiph-web