From: | Andrew Bell |
Date: | 30 Sep 2001 at 21:30:59 |
Subject: | [amiga-c] Re: MyLibrary and SetFunction |
Hi Sensei
On 30-Sep-01, you wrote:
>> Might be useful as an example. The files you'll be interested in are
>> st_patches.c and st_patches.asm. The actual patching is done in C, where
>> the patches themselves are in assembly.
>>
>> Note: Disable PatchControl beforehand, if you're using it. The two seem
>> to conflict.
>
> I'm glad that you said that... Without this note I would not even bother
> to download it, because I was really surprised how it's possible... ;)
>
> Of course there is no conflict, your program is just broken.
> st_patches.c:43c308r missing star... There is load more bugs
> (it's clearly
> visible that it's shit StormC source code,
Well the source code might be shit, but so is your attitude. ;-)
That particular code was developed under Hisoft C++ which is based on Maxon.
You were nearly right.
> there are missing ;
Blame Maxon for this. It doesn't report missing semi-colons beside a closing
"}" brace block.
> and it
> hasn't even bother to report it to you...) but I have to go to sleep...
> You should really write more portable programs next time...
I never said it would compile on anything (other than my own compiler). This
is not GPL code you know. Purely experimental code that *might* be useful to
someone.
> I saw that you
> tried but not enough unfortunately... It takes me lot of time to compile
> it in SAS/C and there is lot of missing __saveds and __asm or even not
> hiding such compiler specific stuffs is not good idea...
Like I said before, as long as it works on my own compiler I'm happy. These
are SAS/C specifics. Where did I say it would compile on SAS/C? I didn't.
Plus, I never used __saveds or similar since that program was compiled as
large code model.
> BTW, SAS/C executable is "just" 50% as large as your StormC original
> one...
Oh, I see, this is a "my compiler is better than your compiler" post? WTF do
I care about executable sizes? That code was not optimized in anyway and
includes debug symbols. WTF do I care if you can compile it or not? I
don't. So stop your whinging.
I released it as an example for patching routines, not as a tutorial on how
to write portable code. If you open the about window you'll notice word
"experimental" take notice next time please before you go around calling
people's work shit.
Something tells me you're just an anti-StormC zealot. If it makes you happy
I don't use Hisoft C++/Maxon anymore. I switched a long time ago. Partly
because of the issues you raised. That particular source was never
recompiled on anything other than Hisoft C++ simply because I haven't
looked at the code since 1999 and I've no plans to update it.
I've no objections to constructive criticisms where people point out
problems and suggest improvements to my code in a *friendly* manner. In
fact, I like feedback from anyone, but that post of yours was on the verge
of being a troll.
Regards, Andrew Bell.
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get your FREE VeriSign guide to security solutions for your web site: encrypting transactions, securing intranets, and more!
http://us.click.yahoo.com/UnN2wB/m5_CAA/yigFAA/dpFolB/TM
---------------------------------------------------------------------~->
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/