Yahoo Web Search

Search results

1. Top results related to what are the disadvantages of structured programming?

   • What are the disadvantages of Aspect-Oriented Programming (AOP)?

     Top Answer

     Answered May 17, 2009 · 8 votes

     • Poor toolchain support - debuggers, profilers etc may not know about the AOP and so may work on code as if all the aspects had been replaced by procedural code
     • Code bloat - small source can lead to much larger object code as code is "weaved" throughout the code base

     Other Answers

     Answered Jun 13, 2014 · 15 votes

     I think the biggest problem is that nobody knows how to define the semantics of an aspect, or how to declare join points non-procedurally.

     If you can't define what an aspect does independently of the context in which it will be embedded, or define the effects that it has in such a way that it doesn't damage the context in which it is embedded, you (and tools) can't reason about what it does reliably. (You'll note the most common example of aspects is "logging", which is defined as "write some stuff to a log stream the application doesn't know anything about", because this is pretty safe). This violates David Parnas' key notion of information hiding. One of the worst examples of aspects that I see are ones that insert synchronization primitives into code; this effects the sequence of possible interactions that code can have. How can you possibly know this is safe (won't deadlock? won't livelock? won't fail to protect? is recoverable in the face of a thrown exception in a synchronization partner?) unless the application only does trivial things already.

     Join points are now typically defined by providing some kind of identifier wildcarding (e.g, "put this aspect into any method named "DataBaseAccess*". For this to work, the folks writing the affected methods have to signal the intention for their code to be aspectized by naming their code in a funny way; that's hardly modular. Worse, why should the victim of an aspect even have to know that it exists? And consider what happens if you simply rename some methods; the aspect is no longer injected where it is needed, and your application breaks. What is needed are join point specifications which are intentional; somehow, the aspect has to know where it is needed without the programmers placing a neon sign at each usage point. (AspectJ has some control-flow related join points which seem a bit better in this regard).

     So aspects are kind of interesting idea, but I think they are technologically immature. And that immaturity makes their usage fragile. And that's where the problem lies. (I'm a big fan of automated software engineering tools [see my bio] just not this way).

     Other Answers

     Answered May 17, 2009 · 8 votes

     I think the biggest disadvantage is using AOP well. People use it in places where it doesn't make sense, for example, and will not use it where it does.

     For example, a factory pattern is obviously something that AOP can do better, as DI can also do it well, but the observer pattern is simpler when using AOP, as is the strategy pattern.

     It will be harder to unit test, esp if you do the weaving at runtime.

     If weaving at runtime then you also take a performance hit.

     Having a good way to model what is going on when mixing AOP with classes is a problem, as UML I don't think is a good model at that point.

     Unless you are using Eclipse then tools do have problems, but, with Eclipse and AJDT AOP is much easier.

     We still use junit and nunit for example, and so have to modify our code to allow unit tests to run, when using priviledged mode AOP could do better unit tests by testing private methods also, and we don't have to change our programs just to make them work with unit-testing. This is another example of not really understanding how AOP can be helpful, we are still chained in many ways to the past with unit-test frameworks and current design pattern implementations and don't see how AOP could help us do better coding.

     Check all answers on Stack Overflow

     1/5

   • What are the advantages and disadvantages of Busy-waiting and timer interrupts in programming?

     Top Answer

     Answered Jan 12, 2016 · 2 votes

     A disadvantage of busy-waiting in embedded devices is the increased power consumption. In a busy wait, the processor is running full-blast, consuming power with no result. Most low power processors have the ability to put the processor to sleep while waiting for a timer interrupt, reducing power consumption dramatically. Lower power consumption = longer battery life.

     Check all answers on Stack Overflow

     2/5

   • What are the disadvantages of the ECS (Entity-Component-System) architectural pattern, compared to OOP (or other paradigms)?

     Top Answer

     Answered Dec 23, 2019 · 11 votes

     Here's a few points I gathered from my research:

     • Systems are very dependent on their ordering. Introducing new systems in between already existing Systems can be a challenge.
     • You also need to plan ahead your data as much as possible, since they will potentially be used by a LOT of systems. Changing the content of components could potentially break quite a few systems.
     • Although it's easy to debug the flow of a system, it's also harder to debug single component changes and not have a global view of what happened to the entity across all it's components. I'm not sure if Unity introduced new debug features for this.
     • If you're planning to use ECS in your team, introducing a new paradigm to devs that are not familiar with it could be a challenge. The onboarding time could be longer with more overhead.

     Hope this gives you a good starting point.

     Check all answers on Stack Overflow

     3/5

   • What are the disadvantages of targeting the JVM instead of x86?

     Top Answer

     Answered Jun 14, 2010 · 4 votes

     Targeting the JVM is a pretty tried and tested approach. The fact that Clojure, Scala, JRuby and many other languages have done so successfully should give you some reassurance.

     My view overall is that the JVM is probably the best target at the moment for new/experimental languages, particularly if you hope to achieve cross platform capability while taking advantage of a truly fantastic JIT compiler and a wealth of very powerful libraries.

     Having said that, the main disadvantages you may encounter targeting the JVM are in my opinion as follows:

     • Lack of tail recursion support at the bytecode level. There are ways around this (e.g. see Clojure's "recur" special form) but it is annoying for some language implementations, particularly functional languages. Will probably eventually be fixed in future versions of Java.
     • Slightly obvious, but you need a JVM installed on your client. Usually not a problem nowadays, but there are still cases where this can be tricky.
     • Primitives (int, long, float etc.) in Java behave differently from the rest of the object system. Again you can work around this but it is some extra hassle for language implementers.

     Some potentially useful/interesting links:

     • ASM bytecode analysis and manipulation framework. This is a great tool, I believe it is what what Clojure uses under the hood.
     • Clojure source code

     Check all answers on Stack Overflow

     4/5

   • what are the disadvantages of H264?

     Top Answer

     Answered Dec 13, 2010 · 7 votes

     Encoding and decoding complexity: H.264 encoding and decoding is more computationally complex than some other codecs such as MPEG-4 Part 2 (DivX, XviD). However, the compression performance of H.264 is significantly better than these so it depends on what is more important to you.

     This is becoming less of a problem as more devices are including hardware support for H.264.

     Error Resiliency: There are some things in H.264 to deal with bit errors, but often they are not used and a single bit error can still have a catastrophic effect. From what I have seen in my study of video codecs, error resiliency seems to being pushed to another layer in most systems. That is, the video codec is designed for maximum compression, and another layer is added on top of the video data to take care of bit errors. That way those who don't need the error resiliency don't pay for it with lower compression rates.

     A common example of this is the DVB standard which uses MPEG-2 or H.264 coded video inside an MPEG-2 Transport Stream that contains a forward error correction scheme.

     Licensing and Royalties: I am no expert (or even reasonably knowledgeable) in this area, but depending on your use case, you may have to pay some kind of royalty to encode to H.264 legally. See this.

     Other than these, I really don't see any other disadvantages of H.264. It seems to be the state of the art for anything from internet quality streamed video to Blue-Ray HD video.

     I can't really comment with regards to the last question (packet/circuit switched networks, interworking between vendors, etc.) since I have never actually built a hardware system to work with H.264. I will say that as long as the encoder creates a valid H.264 stream and you have a decoder that fully implements the standard, you should have no problem getting things to work together. This is the whole point of having a standard.

     Check all answers on Stack Overflow

     5/5

   Show moreShow less

2. People also ask

   What are the advantages and disadvantages of structured programming?

   • Here are some significant advantages and disadvantages of structured programming: Programs are easy to read and understand. They are less prone to errors. Writing code using structured programming requires less time and effort. Locating errors and debugging them is easy. Structured programming enhances the productivity of the development team.

   What is Structured Programming? [Definition, Pros, and Cons] - Techge…

   www.techgeekbuzz.com/blog/what-is-structured-programming/

   See all results for this question

   What are the disadvantages of unstructured programming?

   • Additionally, unstructured programming languages, such as assembly language, lack built-in support for structured programming constructs, making it harder for programmers to adopt a more organized approach. Another drawback of unstructured programming is its limited scalability.

   Structured Programming vs. Unstructured Programming

   thisvsthat.io/structured-programming-vs-unstructured-programming

   See all results for this question

   Why is structured programming bad?

   • All structured programming languages are at risk to overstructuring and loss of efficiency. Structured programming can also be applied incorrectly if the type of structure selected isn't right for the task at hand. The best-known example is the solving of math problems.

   What is Structured Programming? - TechTarget

   www.techtarget.com/searchsoftwarequality/definition/structured-programming-modular-programming

   See all results for this question

   Why is structured programming important in software development?

   • Lastly, it's widely agreed that structured programming improves development time and code quality. These advantages are normally seen as compelling -- even decisive -- and nearly all modern software development employs structured programming.

   What is Structured Programming? - TechTarget

   www.techtarget.com/searchsoftwarequality/definition/structured-programming-modular-programming

   See all results for this question

3. www.geeksforgeeks.org › structured-programmingStructured Programming Approach with Advantages and Disadvantages

   www.geeksforgeeks.org › structured-programming

   • Cached

   Nov 1, 2023 · Advantages of Structured Programming Approach: Easier to read and understand; User Friendly; Easier to Maintain; Mainly problem based instead of being machine based; Development is easier as it requires less effort and time; Easier to Debug; Machine-Independent, mostly. Disadvantages of Structured Programming Approach:

4. gkscientist.com › structured-programmingStructured Programming- Advantages & Disadvantages - GK SCIENTIST

   gkscientist.com › structured-programming

   • Cached

   • Structured Programming
   • Advantages of Structured Programming
   • Disadvantages of Structured Programming

   In structured programming design, programs are broken into functions (also known as modules, subprograms, subroutines, or procedures). Each function is designed to do a specific task with its own data and logic. Information can be passed from one function to another function through parameters. A function can have local data that cannot be accessed...

   See full list on gkscientist.com

   Following are the advantages of structured programming: 1. Decreases the complexity of the program by breaking it down into smaller logical units. 2. Allows several programmers to perform coding simultaneously. 3. Allows common functions to be written once and then used in all the programs needing it. 4. Decreases debugging time, because modules ma...

   See full list on gkscientist.com

   Structured programs generally have redundant codes and are lengthy as compared to unstructured programs.

   Structured programs often use more memory and may execute slower.

   Limiting the structures to three or four basic forms, makes some tasks rather ‘messy’ to perform.

   The completeness of basic logic structures only means that all programs can be implemented with them; it does not mean that a given program can be implemented efficiently or will be bug-free.

   See full list on gkscientist.com

5. www.techgeekbuzz.com › blog › what-is-structuredWhat is Structured Programming? [Definition, Pros, and Cons]

   www.techgeekbuzz.com › blog › what-is-structured

   • Cached

   3 days ago · Advantages and Disadvantages of Structured Programming Here are some significant advantages and disadvantages of structured programming: Advantages Programs are easy to read and understand. They are less prone to errors. They are easier to maintain Writing code using structured programming requires less time and effort.

   • 
   • 
   • 
   • 

6. Videos

   • 

     4:04

     youtube.com

     Introduction to Structured Programming | Structured Programming Advantages & Disadvantages | #1

     Mar 6, 2020

     51.6K Views

   • 

     9:27

     youtube.com

     Advantages and disadvantages of structured programming language || part-5 || LIP™ ||

     Sep 5, 2020

     3.8K Views

   • 

     5:52

     youtube.com

     Introduction To Structured Programming

     Jan 19, 2018

     119.9K Views

   View all

7. www.includehelp.com › data-structure-tutorialStructured Programming, its Advantages and Disadvantages

   www.includehelp.com › data-structure-tutorial

   • Cached

   Sep 25, 2017 · Disadvantages of structured programming. The following are the disadvantages of structured programming: A high level language has to be translated into the machine language by translator and thus a price in computer time is paid. The object code generated by a translator might be inefficient compared to an equivalent assembly language program.

8. www.techtarget.com › searchsoftwarequalityWhat is Structured Programming? - TechTarget

   www.techtarget.com › searchsoftwarequality

   Disadvantages of structured programming. The biggest disadvantage of structured programming is a reduction in execution efficiency, followed by greater memory usage. Both these problems arise from the introduction of calls to a module or process, which then returns to the caller when it's done.

   • Author: Tom Nolle

9. en.wikipedia.org › wiki › Structured_programmingStructured programming - Wikipedia

   en.wikipedia.org › wiki › Structured_programming

   • Cached

   Structured programming. Structured programming is a programming paradigm aimed at improving the clarity, quality, and development time of a computer program by making extensive use of the structured control flow constructs of selection ( if/then/else) and repetition ( while and for ), block structures, and subroutines .

10. thisvsthat.io › structured-programming-vsStructured Programming vs. Unstructured Programming

    thisvsthat.io › structured-programming-vs

    • Cached

    It can sometimes lead to code duplication, especially when multiple functions or subroutines require similar code segments. Additionally, the strict adherence to structured programming principles can sometimes limit the flexibility and creativity of programmers, especially in situations where unconventional solutions are required.