| [Web] AmigaOS4 Snapshots from SDK | ANN.lu |
| Posted on 20-Apr-2004 10:17 GMT by Mikey C (Edited on 2004-04-20 21:29:25 GMT by Christian Kemp) | 57 comments
View flat
View list | |
Nicolas Mendoza was kind enough to provide a few snapshots of the different development tools you'll be able to play with when the AmigaOS 4.0 Developer Pre-release CD arrives.
View Screenshots at Amigaworld.net
|
|
| List of all comments to this article |
| AmigaOS4 Snapshots from SDK : Comment 56 of 57 | ANN.lu |
| Posted by Kjetil on 23-Apr-2004 05:05 GMT | In reply to Comment 53 (darklite):
Personally I can’t se how a program.exe sized to be 25mb can be any good, a good program should reuse it’s on features all over the place so it becomes consistent, the readability of the code becomes bad if the program it self is not written inn a way, that is not modular,
The biggest problem whit large projects are that you have 20 developers doing separate parts of the project, there are room for not knowing about features or functions that are already created, that can do the job all ready, then there is the chicken and the egg problem, if the modules are not ready to work inn joint venture, what do you do? Duplicate an other module as dummy function call’s, supposedly remember to remove them after it’s all done.
Then there is the other issue, copy& paste programming, well you have a function and you need a function that do about the same only not quite. Programs written this way tend to be extremely large (duplicated 2-20 times), hard to edit; you can’t change one function to change the behaviour you need to edit a bunch of functions , it might be that you need optimized routines for different gfx modes, then this can be more efficient then, writing a common function. The most common excuse for using copy & paste is to cut time or for testing, there for you end up whit a lot of not optimized functions,
Suffocation programming, if you are one of this HI-level programs writing interpreted code, and using over complicated objects larger then you program, and you only tend to use one feature of that object, what a waste of CPU time, and disk space, shore you get it done, inn short week, then you go about hardware upgrade cycles.
If you think you know a programming language and you really do not, do you know what pointer is, do you know what “typedef struct” or “function pointer” is? And do you use them?
Not knowing your program language can make your program slower the Basic. |
|
| List of all comments to this article (continued) |
|
- User Menu
-
- About ANN archives
- The ANN archives is powered by #AmigaZeux. It was updated daily (news last: 22-Oct-2004; comments last: 18-May-2005).
ANN.lu was created, previously owned and maintained by Christian Kemp, www.ckemp.com.
- Contribute
- Not possible at this time!
- Search ANN archives
- Advanced search
- Hosting
- ANN.lu was hosted by Dreamhost. Sign up through this link, mention "ckemp" as referrer and he will get a 10% commission on any account you purchase.
Please show your appreciation for any past, present and future work on ANN.lu by making a contribution via PayPal.
|
