Yahoo Web Search

Search results

1. • • Declarative programming is where you say what you want without having to say how to do it. With procedural programming, you have to specify exact steps to get the result. For example, SQL is more declarative than procedural, because the queries don't specify steps to produce the result.
     stackoverflow.com › questions › 1619834

     What is the difference between declarative and procedural ...

2. Top results related to is procedural programming a step toward declarative programming?

   • Programming a game, Code executing is random

     Top Answer

     Answered Jul 25, 2012 · 3 votes

     OK. I've tried it and it works ok, but you don't print anything when the monster misses, is this what you mean by random failure? To rectify it, simply append an else to the condition:

     hitchance = rand.Next(0, 100);if (hitchance > 30){ attackdamage = CH.GetMonsterDamage(rand); Console.WriteLine("The Monster Attacks!"); if (battlechoice == "d" || battlechoice == "D") { //this is so that defend has some sort of benefit attackdamage /= 2; } heroHitPoints -= attackdamage;//subtract the damage Console.WriteLine("The Hero loses {0}hp", attackdamage);}else{ Console.WriteLine("The monster misses!");}

     Check all answers on Stack Overflow

     1/5

   • Programming style: should you return early if a guard condition is not satisfied?

     Top Answer

     Answered May 28, 2010 · 40 votes

     I prefer the first style, except that I wouldn't create a variable when there is no need for it. I'd do this:

     // Style 3public SomeType aMethod() {- if (!guardCondition()) { return null; } SomeType result = new SomeType(); doStuffToResult(result); doMoreStuffToResult(result); return result;}

     Other Answers

     Answered May 28, 2010 · 29 votes

     Having been trained in Jackson Structured Programming in the late '80s, my ingrained philosophy was always "a function should have a single entry-point and a single exit-point"; this meant I wrote code according to Style 2.

     In the last few years I have come to realise that code written in this style is often overcomplex and hard to read/maintain, and I have switched to Style 1.

     Who says old dogs can't learn new tricks? ;)

     Other Answers

     Answered Dec 22, 2021 · 16 votes

     Style 1 is what the Linux kernel indirectly recommends.

     From https://www.kernel.org/doc/Documentation/process/coding-style.rst, chapter 1:

     Now, some people will claim that having 8-character indentations makes the code move too far to the right, and makes it hard to read on a 80-character terminal screen. The answer to that is that if you need more than 3 levels of indentation, you're screwed anyway, and should fix your program.

     Style 2 adds levels of indentation, ergo, it is discouraged.

     Personally, I like style 1 as well. Style 2 makes it harder to match up closing braces in functions that have several guard tests.

     Check all answers on Stack Overflow

     2/5

   • Programming-General: What are the 5 stages in which a source code is transformed to a executable file?

     Top Answer

     Answered May 27, 2010 · 5 votes

     The five stages are bogus. Standard ML of New Jersey, for example, was at one point a 33-pass compiler, going from source code to machine code (no textual assembly; it blasts machine code right into memory). I doubt there are exactly five representations that the code goes through. In the lcc C compiler there are these representations:

     • Unpreprocessed source
     • Preprocessed source
     • IR Dags
     • Textual assembly
     • Relocatable object code
     • Executable binary

     These days most other compilers translate source into abstract syntax, and in fact the designers of lcc said in retrospect that they wish they had used abstract-syntax trees.

     This seems like one of those sad situations where you need to find out what your instructor wants to hear and regurgitate it back. And don't take it too seriously.

     Check all answers on Stack Overflow

     3/5

   • Programming code that predicts which day of the week it is when given a specific date

     Top Answer

     Answered Sep 27, 2017 · -2 votes

     The line boolean c = 0 <= d0 <= 6; should be boolean c = 0 <= d0 && d0 <= 6;

     Take a look at the java specs to get an idea of how to use relational operators.

     Basically 1 < 0 is of the type boolean and you cannot use smaller than and greater than on a boolean.

     Check all answers on Stack Overflow

     4/5

   • Programming a 2D grid in Java

     Top Answer

     Answered Jun 19, 2011 · 9 votes

     If you're not worrying about speed or memory too much, you can simply use a 2D array - this should work well enough.

     If speed and/or memory are issues for you then this depends on memory usage and the access pattern.

     A single dimensional array is the way to go if you need high performance. You compute the proper index as y * wdt + x. There are 2 potential problems with this: cache misses and memory usage.

     If you know that your access pattern is such that you fetch neighbours of an element most of the time, then mapping a 2D space into a 1D array as described above may cause cache misses - you want the neighbours to be close in memory, and neighbours from 2 different rows are not. You may have to map your 2d tiles in a different order to your 1d array. See Hilbert curves for example.

     For better memory usage, if you know that most of your tiles are always the same (e.g. always grass), you might want to implement a sparse array or a quad tree. Both can be implemented quite efficiently, with cache awareness in mind (the sparse array link is good example for this). Another benefit is that these can be dynamically extended. However, you will always have to pay extra levels of indirection in the end for this to work.

     NOTE: Be careful with using generic classes such as HashMaps with the key type being some primitive type or a special location class if you're worried about performance - you will either have to allocate an object each time you index the hash map or pay the price of boxing/unboxing. In addition to this, hash maps will not allow you efficient spatial queries (e.g. give me all objects existing in the radius R of a given object - quad trees are better for this).

     Check all answers on Stack Overflow

     5/5

   Show moreShow less

3. People also ask

   What is the difference between declarative programming and procedural programming?

   • Declarative programming is where you say what you want without having to say how to do it. With procedural programming, you have to specify exact steps to get the result. For example, SQL is more declarative than procedural, because the queries don't specify steps to produce the result. +1 for good example on SQL. can we have more examples please?

   What is the difference between declarative and procedural programming

   stackoverflow.com/questions/1619834/what-is-the-difference-between-declarative-and-procedural-programming-paradigms

   See all results for this question

   What is declarative programming?

   • Declarative programming is a programming paradigm that focuses on describing what you want to happen, rather than how you want it to happen. In other words, you tell the computer what you want to achieve, and it figures out the best way to do it. One of the most popular examples of declarative programming is SQL.

   Declarative vs Procedural Programming Whats the Difference

   declarative.dev/article/Declarative_vs_Procedural_Programming_Whats_the_Difference.html

   See all results for this question

   What is the difference between procedural programming and data centric programming?

   • Data-centric: Declarative languages are particularly well-suited for working with large datasets and performing complex analytical queries. Definition: Procedural programming involves writing step-by-step instructions that specify the sequence of operations to achieve a desired outcome.

   Declarative vs Procedural Programming: A Comparison

   mentor.enterprisedna.co/queries/declarative-vs-procedural-programming-paradigms

   See all results for this question

   Why is procedural programming classified as imperative programming?

   • Procedural programming is classified as a imperative programming, because it involves direct command of execution. Procedural is a sub-class of imperative since procedural includes block and scope concepts, whereas imperative describes a more general concept that does not require such features.

   Procedural programming - Wikipedia

   en.wikipedia.org/wiki/Procedural_programming

   See all results for this question

4. stackoverflow.com › questions › 1619834What is the difference between declarative and procedural ...

   stackoverflow.com › questions › 1619834

   • Cached

   Oct 25, 2009 · Declarative programming is where you say what you want without having to say how to do it. With procedural programming, you have to specify exact steps to get the result. For example, SQL is more declarative than procedural, because the queries don't specify steps to produce the result.

   • Imperative. There are several sub-paradigms of the imperative programming paradigm, such as the procedural or the object-oriented programming para...
   • Let me give you a real-world example: I need a cup of tea. Procedural: Go to kitchen. Get sugar, milk, and tea, Mix them, and heat over the fir...
   • Procedural Programming : In procedural programming, when the program starts, it follows a set of instructions. The instructions may change based o...
   • The main difference between two programming languages are, In procedural programming, we tell the computer how to solve the problem and in declarat...
   • To address the ansible comment and maybe provide an example between the differences of the two. Ansible is procedural where as something like puppe...

5. declarative.dev › article › Declarative_vsDeclarative vs Procedural Programming Whats the Difference

   declarative.dev › article › Declarative_vs

   • Cached

   With declarative programming, you're describing what you want to happen, and the computer figures out the best way to do it. With procedural programming, you're describing the exact steps that the computer should take to achieve a particular outcome, which can be less flexible.

6. www.freecodecamp.org › news › an-introduction-toProgramming Paradigms – Paradigm Examples for Beginners

   www.freecodecamp.org › news › an-introduction-to

   • Cached

   • What Is A Programming Paradigm?
   • What A Programming Paradigm Is Not
   • Why Should I Care?
   • Popular Programming Paradigms

   Programming paradigms are different ways or styles in which a given program or programming language can be organized. Each paradigm consists of certain structures, features, and opinions about how common programming problems should be tackled. The question of why are there many different programming paradigms is similar to why are there many progra...

   See full list on freecodecamp.org

   Programming paradigms are not languages or tools. You can't "build" anything with a paradigm. They're more like a set of ideals and guidelines that many people have agreed on, followed, and expanded upon. Programming languages aren't always tied to a specific paradigm. There are languages that have been built with a certain paradigm in mind and hav...

   See full list on freecodecamp.org

   Short answer: general knowledge. Long answer: I find that it's interesting to understand the many ways in which programming can be done. Exploring these topics is a good way of opening your mind and helping you think outside the box and outside the tools you already know. Moreover, these terms are used a lot in the coding world, so having a basic u...

   See full list on freecodecamp.org

   Now that we have introduced what programming paradigms are and are not, let's go through the most popular ones, explain their main characteristics, and compare them. Keep in mind this list is not exhaustive. There are other programming paradigms not covered here, although I'll be covering the most popular and most widely-used ones.

   See full list on freecodecamp.org

7. Videos

   • 

     9:48

     youtube.com

     Procedural-Oriented Programming

     Oct 16, 2022

     8.9K Views

   • 

     39:28

     youtube.com

     Declarative Programming | Part 1 | A Level | By ZAK

     Sep 6, 2020

     1.5K Views

   • 

     7:17

     study.com

     Object-Oriented Programming vs. Procedural Programming

     Dec 3, 2013

     543K Views

   View all

8. mentor.enterprisedna.co › queries › declarative-vsDeclarative vs Procedural Programming: A Comparison

   mentor.enterprisedna.co › queries › declarative-vs

   • Cached

   Declarative programming focuses on what you want to achieve, while procedural programming involves step-by-step instructions. Examples and advantages of each paradigm are discussed, as well as considerations for choosing the right approach in advanced analytics.

9. declarative.dev › article › Declarative_vs"Declarative vs. Procedural Programming: Which is Right for ...

   declarative.dev › article › Declarative_vs

   • Cached

   Procedural programming is a programming paradigm that emphasizes sequences of steps. It is characterized by defining a specific set of actions to achieve a particular outcome. In contrast to declarative programming, procedural programming is better suited for implementation details in code.

10. en.wikipedia.org › wiki › Procedural_programmingProcedural programming - Wikipedia

    en.wikipedia.org › wiki › Procedural_programming

    • Cached

    A skilled logic programmer uses the procedural interpretation to write programs that are effective and efficient, and uses the declarative interpretation to help ensure that programs are correct. See also. Comparison of programming paradigms; Declarative programming; Functional programming (contrast) Imperative programming; Logic programming

11. en.wikipedia.org › wiki › Comparison_of_programmingComparison of programming paradigms - Wikipedia

    en.wikipedia.org › wiki › Comparison_of_programming

    • Cached

    Declarative programming – focuses on what to execute, defines program logic, but not detailed control flow. The following are widely considered the main programming paradigms, as seen when measuring programming language popularity: Procedural programming – specifies the steps a program must take to reach a desired state.