Layers.library V45 on the aminet

[Cosmos]

The problem with the new layers.library
http://amiga.ct8.pl/wp-content/uploads/2014/08/MOV_0017.mp4

I discovered a compilator branch bug into the rtg.library v40.3994...

Only 4 or 6 bytes to fix, and I'll send you this new version for checking...

[Cosmos]

Would you *please* stop messing with other's people software? This is Alex' decision, and not yours, and also not mine. If I say I'll keep care of it, I'll keep care of it, but it will take as long as it takes.

I sent a message to Alex on facebook and no answer...

[Cosmos]

And that gives you which right? Exactly... none-so-ever. Would it help to mention that I had contact with him just months ago? And that we had a friendly exchange on the P96 subject?  Ok, point is that I do not exactly know what the legal situation with P96 is and wether Alex can even decide what can happen with it. But you or me can do that to an even lesser degree. The situation might be delicate, it is delicate to me, and it is probably even more delicate to Alex, I really don't know, but all I can do is to find out and understand where we are.   Now, instead of trying to have some patience and thrusting people that they'll try to do their job properly to their best of their knowledge, you just jump ahead and ruin the entire situation. Thank you for that so much.

And I emailed Tobias about 2 months ago for another reason, and no answer too...

Amiga Classics are old now, they don't care...


Finally I checked this morning the rtg.library branch bug : I changed only one byte ($00 instead of the wrong $04)

Emailed to Pawelek for checking...

[Cosmos]

It's totally impossible to talk with Thomas Richter : he change is mind like a girl change his clothes...


In June 2014 :

I will likely not have the time to keep it updated. Bug reports
welcome, of course, but without promise that I will provide fixes. If you find
problems, you are on your own. De-install by removing layers.library from LIBS:
and remove the corresponding argument from LoadModule, you should be fine again.

In August 2014 :

With all necessary respect: If you find a bug (or believe to have found a bug, I don't know), please *report it* so it can be fixed upstream.

Where is the logic ? He wrote everything and it's contaire...



Anyways, the branch bug in the rtg.library is really a very big bug : $6004FDA6 must be replaced by $6000FDA6

A bug from the compilator SAS/C, not from the coders I guess well...

Check by yourself, and see...

[Cosmos]

You still don't get it, right? I'm trying to find out what the situation is, understood? How much more explicit do I need to get?   Have you made any measurements showing the efficiency of these "improvements", and have you considered that this leaves the libraries in a pretty unmaintainable state?  

Again, what is "working" for you? For me it means that I can also fix something in two years in the future. With the kind of "improvements" I see from Cosmos this is unlikely to be even possible. First of all, it doesn't really improve anything, and second, even if the results were measurable, the improvements were lost or incompatible to any other changes that had to be made.

Have you watching my changes into my code ? Certainly no...

For example, the function R_AndRegionRegion in the graphics.library use two AllocMem (and of course two FreeMem at the end) for two tiny buffers (only $C) : I replaced by six clr.l -(sp) for these buffers on the stack now...

This function is now more than 1000 times faster, so the improvement is real...


You are a professionnal troller, you talk in the void, you have lost all credibility...

[Cosmos]

I have a dream. I'd like to see ThoR and Cosmos working intelligently together without killing each other, each in his field of expertise.
 
But unfortunately, since I saw the little mouse to be eaten by the cat, I do not believe in Christmas.

I only wanna explain that the quality of the code is very important.

(Thomas Richter still compilling most of his programms (like BenchTrash for example) with the -68000 option. BenchTrash is a part of the OS 3.9 who is 68020+ only...)


These mistakes are done by all the other actors in the computers world like Microsoft or Apple : they bypass the quality of the code using crappy compilators most of the time...

With my reworked libraries, I do exactly the opposite : I simpifly the code and make it smaller...

Another example with my 6 autovectors in the exec.library : original ones take 544 bytes. Now with good coding, only 130...

[Cosmos]

The largest scale Amiga program I have written in assembler is ViNCed, which is about 63000 lines assembler. It is *barely* managable in that size. It's hard to change, and its hard to maintain

Because you are still a beginner in asm : you have a lot of thing to learn, and me too in other domains of course... We have all to learn all !!

You take your case for a generality... Big mistake !


The 68k is certainly the only CPU who large programms are fully possible in asm only...

For exemple, the W3D_Permedia2.library is 276 615 lines long and I make any changes very easly...

[Cosmos]

There are three books which profoundly changed how I work. These are "Debugging the development process", "Writing solid code" and "Code complete". The first two were written by Steve Maguire and are probably out of print (but can be bought used rather cheaply). The last was written by Steve McConnell and is still in print. If you are going to read just one of these books, make it "Code complete". The drawback of "Code complete" is that it's rather long, though, while the other two books are shorter. However, I found that reading "Code complete" is exceptionally rewarding. Every chapter you read will change how you work and build software, if you are willing to question the way how you work today.http://www3.cs.stonybrook.edu/~algorith/, don't miss it.

For me, learning from books is a mistake : the better and best way is to learn by yourself.

Start learning with tiny programms, understand how they works, modify them...

Little by little, your skill will grow up. When you don't understand something, email a confirmed coder (by not Thomas Richter, please !) for explanations... And so on...

I do that for me and I reached an high level...


Good luck !!

[Cosmos]

I have to disagree with you on that.

The best way to learn is to experiment/explore, make mistakes and find out why you made them, then avoid making them again if possible. The problem with making mistakes is knowing when you are making them.

If you are lucky, you will, after a while, realize by yourself that you made a mistake or left an alternative option to solve a problem unexplored.

You don't always get lucky. It's by far more effective to know somebody who understands your work, can give you his opinion on it and offer insights.

A third person may be able to tell you when you are on the wrong track, drawing the wrong conclusions or have falsely convinced yourself of having explored a problem to the fullest. All by yourself you are far less likely to arrive at the same conclusion.

There's a term for that: confirmation bias. Don't believe that you are immune, you're human like the rest of us.

No, no, sorry : the authors of your books will "programm" the readers beginner to follow a way...

I started asm using 2 books and the result was a give up : I understood few things only...

After some years, I started again with my method described above, and this time it works good for me...

I wrote my story here (in french, but you can translate using "Traduction" on the left) : http://assembly68k.blogspot.fr/p/blog-page_24.html

For me, the best is to learn by yourself, to "build" YOUR own way with using (and developping) your imagination and understanding...


Anyway, do what you feel better for you, I just give here my opinion and my experience...