写给所有程序员_你的逻辑不要太贪心

本文探讨了编程中常见的“贪心”现象,包括函数、选择结构、循环结构和变量的贪心使用,并通过实例展示了如何重构代码以提高其可读性和维护性。

有的时候,可能一段逻辑代码需要大量的运算,为了偷懒,我们把本不该写在一起的东西勉强拼凑在一起。

1.贪心的函数(贪心的方法)

例子:

public static void main(String[]args){
    int firstNum = 5;
    int secondNum = 3;
    System.out.println(getSumOfTwoNums(firstNum,secondNum));
    //doSomething...
    System.out.println(getSumOfTwoNums(5,2));
}

public static int getSumOfTwoNums(int firstNum,int secondNum){
    ++firstNum;
    return firstNum + secondNum;
}

发现问题了吗?求和函数(方法)里面竟然有一句++firstNum;!!!第一次用的时候,可能是因为某种需要,所以需要把firstNum加一。为了方便,把它和后面的相加写在一起了。这样后面用的时候可能导致错误,因为后面用到的时候你已经忘记了这个函数(方法)里面你居然一时脑抽把加一这样的代码写在里面了。
贪心:你的函数和方法把没提到的事顺便做了。
修改:不要做你的函数(方法)没有提到的事,这可能导致你后面的调用造成隐患。

正确的做法:

public static void main(String[] args){
    int firstNum = 5;
    int secondNum = 3;
    System.out.println(getSumOfTwoNums(firstNum+1,secondNum));
    //doSomething...
    System.out.println(getSumOfTwoNums(5,2));
}

public static int getSumOfTwoNums(int firstNum,int secondNum){
    return firstNum + secondNum;
}

2.贪心的选择结构

public static void main(String[] args){
    int CODE_A = 1;
    int CODE_B = 2;

    //doSomething

    int firstNum = 5;
    int secondNum = 3;
    int thirdNum  8;
    int fourthNum = 2;

    int sum = 0;
    int difference = 0;
    if(CODE_A > CODE_B){
        sum = thirdNum  + fourthNum;
        difference = fourthNum - thirdNum;
    }else if(CODE_A == CODE_B){
        difference = firstNum - secondNum;
    }else{
        sum = thirdNum  + secondNum;
    }
}

上面的例子要讲的是达到某些条件要做一些操作,暂时以CODE_A,CODE_B为例子,表示某状态暂时以这种方式代替。sum表示求的和,difference表示求的差。
贪心:把这两个逻辑写在同一段代码里面了,虽然两者并没有关系。
修改:把不同部分的代码逻辑分开。
正确的做法:

public static void main(String[] args){
    int CODE_A = 1;
    int CODE_B = 2;

    //doSomething

    int firstNum = 5;
    int secondNum = 3;
    int thirdNum  8;
    int fourthNum = 2;

    int sum = 0;
    if(CODE_A > CODE_B){
        sum = thirdNum  + fourthNum;
    }else if(CODE_A < CODE_B){
        sum = thirdNum  + secondNum;
    }

    int difference = 0;
    if(CODE_A > CODE_B){
        difference = fourthNum - thirdNum;
    }else if(CODE_A == CODE_B){
        difference = firstNum - secondNum;
    }
}

可以看到,虽然代码判断了两次,但是逻辑更清晰了,因为很多时候,贪心并不满足全匹配,这个改一下,那个又改一下,可能你第一次写的时候很爽:只要写一次。但后面看的时候,保证你会疯掉。而且,贪心写法,不方便分割,像上面的代码,可以改成这样:

选择结构贪心识别:一个选择结构if…else if(…)…else不能使用一个函数(方法)表达出来

public class TestGreedy{
    private int CODE_A = 1;
    private int CODE_B = 2;

    int firstNum = 5;
    int secondNum = 3;
    int thirdNum  8;
    int fourthNum = 2;

    public static void main(String[] args){
        TestGreedy greedy = new TestGreedy();

        int sum = getSumByCode();
        int diference = getDifferenceByCode();
    }

    public int getSumByCode(){
        if(CODE_A > CODE_B){
            return thirdNum  + fourthNum;
        }else if(CODE_A < CODE_B){
            return thirdNum  + secondNum;
        }
        return 0;
    }

    public int getDifferenceByCode(){
        if(CODE_A > CODE_B){
            return fourthNum - thirdNum;
        }else if(CODE_A == CODE_B){
            return firstNum - secondNum;
        }
        return 0;
    }
}

因为不贪心,所以if…else存在完整的逻辑含义,所以我们可以把它们单独放到函数(方法)里面,这样看起来,马上清爽了,而这种做法的前提是:不要太贪心,又求和又求差,很难以一个函数(方法)表达它的意思。

补充:特殊情况:点击控件的识别和数据返回,这种情况不属于逻辑问题导致的,不作为贪心逻辑理论的考虑范围。

public void onClick(View v){
    swich(v.getId()){
        case ...:break;
        case ...:break;
    }
}

3.贪心的循环结构

public static void main(String[] args){
        TestGreedy greedy = new TestGreedy();

        int arrNums = new int[]{2,4,5,6};

        int sum = 0;
        int muti = 1;
        for(int i = 0; i < arrNums.size(); i++){
            sum += arrNums[i];
            muti *= arrNums[i];
        }
    }

贪心:一个循环里面做了多件事
首先,不能不承认,你很“聪明”,从逻辑的角度讲你把O(2n)的时间复杂度降低到O(n)。但实际上,它的指数级别还是一样的,都是n级别!!!。除非数据量非常大(数组级别在千万以上),否则这样做除了搞乱逻辑只外,实在没有什么太重大的意义。

修改后的代码:

public static void main(String[] args){
        int[] nums = new int[]{2,4,5,6};

        int sum = 0;
        for(int i = 0; i < nums .size(); i++){
            sum += nums [i];
        }

        int muti = 1;
        for(int i = 0; i < nums .size(); i++){
            muti *= nums [i];
        }
}

同样,我们可以单独把它拆分到单独的函数或者方法当中:

public static void main(String[] args){
        int[] nums = new int[]{2,4,5,6};

        int sum =   getSumOfNums(nums);
        int muti = getMutiOfNums(nums);
}

public static int getSumOfNums(int[] nums){
    int sum = 0;
    for(int i = 0; i < nums .size(); i++){
        sum += nums [i];
    }
}

public static int getMutiOfNums(int[] nums){
    int muti = 1;
    for(int i = 0; i < nums .size(); i++){
        muti *= nums [i];
    }
}

循环结构贪心识别:一个选择结构for(…){}不能使用一个函数(方法)表达出来

4.贪心的变量

public static void main(String[] args){
        int sum = 0;
        for(int i = 0; i < arrNums.size(); i++){
            sum += arrNums[i];
        }
        sum -= 5;
        System.out.println(sum);
    }

你的和有表达它会减少的含义么?你确定这样使用不会出错?在我看来,这种一个变量两种用途的方式,除了给你后面的代码造成困惑和麻烦外,没什么太有用的地方,正确的写法是:

public static void main(String[] args){
        int sum = 0;
        for(int i = 0; i < arrNums.size(); i++){
            sum += arrNums[i];
        }
        int offsetSum -= 5;
        System.out.println(offsetSum);
    }

贪心变量的特点是,你对变量做了某件事情,可完全无法用原有的变量名称看出它有表达有做这件事情的意向

实例

补充:一直在想一个例子,怎么讲不贪心的好处更加具体,然后重新改了一下公司一个计算价格的逻辑,当然,由于保密不能贴出来,所以打算用一个叫外卖的例子,因为这个可以足够复杂。

假设收外卖费是这样收的(虚拟的,非真实):外卖费由食物费,餐具费,送货费,红包,优惠(满100-22)组成,然后计算。

public double getTakeOutFoodCost(){
    double foodCost = 0;
    double tableWareCost = 0;
    double redPacketCost = 0;
    double realCost = 0;//实际价格(不减)
    double fillSubMoney = 0;

    for(FoodBean foodBean:foodBeans){
        foodCost += foodBean.getCost();
    }

    takeOutBean.setFoodCost(foodCost);

    tableWareCost = takeOutBean.getNumOfPeople() * takeOutBean.getSingleTableWareCost();

    takeOutBean.setTableWareCost(tableWareCost);

    if(takeOutBean.getRedPacketCost()!=0){
        takeOutBean.setCostByRedPacket(1);
        redPacketCost = takeOutBean.getRedPacketCost();
        foodCost = (foodCost -tableWareCost.getRedPacketCost()>0)?foodCost -tableWareCost.getRedPacketCost():0;
        if(takeOutBean.needDeliveryCost())
            foodCost += foodBean.getDeliveryCost();
        realCost = foodCost + tableWareCost+foodBean.getDeliveryCost()+tableWareCost.getRedPacketCost();
    }else{
        takeOutBean.setCostByRedPacket(0);
        if(takeOutBean.needDeliveryCost())
            foodCost += foodBean.getDeliveryCost();
        realCost = foodCost + tableWareCost+foodBean.getDeliveryCost();
    }

    takeOutBean.setRealCost(realCost);

    fillSubMoney = realCost/100 * 22;

    takeOutBean.setFillSubMoney(fillSubMoney);
    return  foodCost + tableWareCost - redPacketCost - fillSubMoney;
}

首先,我们分析到这个函数(方法)本质是让我们获取各种价钱,然后返回的。但是这个方法里面放了太多的东西(实际还好,我看的那个有五层if…):
1.这个方法名说明了是用于获取外卖价钱的,但此方法对于takeOutBean(外卖对象)以各种姿势进行设置,你确定以后还能找的到?

2.foodCost,这应该指的是食物费吧?为何要减红包费,为何要加送货费?注意到你的realCost实际上把快递费算了两次吗?注意到最后又减了一次红包吗?这就是变量贪心的后果。

3.以下代码再if,else都有写到,这是贪心太多,自己都看不清代码的时候,很容易犯的错误,实际上,当你的代码够少,逻辑不贪心的时候完全不会犯这样的错误:

if(takeOutBean.needDeliveryCost())
            foodCost += foodBean.getDeliveryCost();

好了,现在对这个复杂的函数进行改造。

第一步,分离takeOutBean的设置和价格计算部分

public void payMoney(){
    int takeOutFoodCost = getTakeOutFoodCost();
    setTakeOutBeanData();
    //doSomething
}

public void setTakeOutBeanData(){

}

大致结构是这样的,然后我们先把getTakeOutFoodCost()的代码复制一份到setTakeOutBeanData()里面变成:

public void payMoney(){
    int takeOutFoodCost = getTakeOutFoodCost();
    setTakeOutBeanData();
    //doSomething
}

public void setTakeOutBeanData(){
    double foodCost = 0;
    double tableWareCost = 0;
    double redPacketCost = 0;
    double realCost = 0;//实际价格(不减)
    double fillSubMoney = 0;

    for(FoodBean foodBean:foodBeans){
        foodCost += foodBean.getCost();
    }

    takeOutBean.setFoodCost(foodCost);

    tableWareCost = takeOutBean.getNumOfPeople() * takeOutBean.getSingleTableWareCost();

    takeOutBean.setTableWareCost(tableWareCost);

    if(takeOutBean.getRedPacketCost()!=0){
        takeOutBean.setCostByRedPacket(1);
        redPacketCost = takeOutBean.getRedPacketCost();
        foodCost = (foodCost -tableWareCost.getRedPacketCost()>0)?foodCost -tableWareCost.getRedPacketCost():0;
        if(takeOutBean.needDeliveryCost())
            foodCost += foodBean.getDeliveryCost();
        realCost = foodCost + tableWareCost+foodBean.getDeliveryCost()+tableWareCost;
    }else{
        takeOutBean.setCostByRedPacket(0);
        if(takeOutBean.needDeliveryCost())
            foodCost += foodBean.getDeliveryCost();
        realCost = foodCost + tableWareCost+foodBean.getDeliveryCost();
    }

    takeOutBean.setRealCost(realCost);

    fillSubMoney = realCost/100 * 22;

    takeOutBean.setFillSubMoney(fillSubMoney);
    return  foodCost + tableWareCost - redPacketCost - fillSubMoney;
}

public double getTakeOutFoodCost(){
    double foodCost = 0;
    double tableWareCost = 0;
    double redPacketCost = 0;
    double realCost = 0;//实际价格(不减)
    double fillSubMoney = 0;

    for(FoodBean foodBean:foodBeans){
        foodCost += foodBean.getCost();
    }

    takeOutBean.setFoodCost(foodCost);

    tableWareCost = takeOutBean.getNumOfPeople() * takeOutBean.getSingleTableWareCost();

    takeOutBean.setTableWareCost(tableWareCost);

    if(takeOutBean.getRedPacketCost()!=0){
        takeOutBean.setCostByRedPacket(1);
        redPacketCost = takeOutBean.getRedPacketCost();
        foodCost = (foodCost -tableWareCost.getRedPacketCost()>0)?foodCost -tableWareCost.getRedPacketCost():0;
        if(takeOutBean.needDeliveryCost())
            foodCost += foodBean.getDeliveryCost();
        realCost = foodCost + tableWareCost+foodBean.getDeliveryCost()+tableWareCost;
    }else{
        takeOutBean.setCostByRedPacket(0);
        if(takeOutBean.needDeliveryCost())
            foodCost += foodBean.getDeliveryCost();
        realCost = foodCost + tableWareCost+foodBean.getDeliveryCost();
    }

    takeOutBean.setRealCost(realCost);

    fillSubMoney = realCost/100 * 22;

    takeOutBean.setFillSubMoney(fillSubMoney);
    return  foodCost + tableWareCost - redPacketCost - fillSubMoney;
}

代码暂时性的变多了,看的好乱,好想吐。。。为了整洁,为了优雅,为了不贪心,我们姑且忍受,现在,我们把所有getTakeOutFoodCost()中设置takeOutBean的部分全部删掉,把setTakeOutBeanData()的所有非takeOutBean设置部分全部删掉:

第二步,删除getTakeOutFoodCost()设置takeOutBean的部分,删除setTakeOutBeanData()的所有非takeOutBean设置部分

public void payMoney(){
    int takeOutFoodCost = getTakeOutFoodCost();
    setTakeOutBeanData();
    //doSomething
}

public void setTakeOutBeanData(){
    takeOutBean.setFoodCost(foodCost);
    takeOutBean.setTableWareCost(tableWareCost);

    if(takeOutBean.getRedPacketCost()!=0){
        takeOutBean.setCostByRedPacket(1);
    }else{
        takeOutBean.setCostByRedPacket(0);
    }

    takeOutBean.setRealCost(realCost);
    takeOutBean.setFillSubMoney(fillSubMoney);
}

public double getTakeOutFoodCost(){
    double foodCost = 0;
    double tableWareCost = 0;
    double redPacketCost = 0;
    double realCost = 0;//实际价格(不减)
    double fillSubMoney = 0;

    for(FoodBean foodBean:foodBeans){
        foodCost += foodBean.getCost();
    }

    tableWareCost = takeOutBean.getNumOfPeople() * takeOutBean.getSingleTableWareCost();

    if(takeOutBean.getRedPacketCost()!=0){
        foodCost = (foodCost -tableWareCost.getRedPacketCost()>0)?foodCost -tableWareCost.getRedPacketCost():0;
        if(takeOutBean.needDeliveryCost())
            foodCost += foodBean.getDeliveryCost();
        realCost = foodCost + tableWareCost+foodBean.getDeliveryCost()+tableWareCost;
    }else{
        if(takeOutBean.needDeliveryCost())
            foodCost += foodBean.getDeliveryCost();
        realCost = foodCost + tableWareCost+foodBean.getDeliveryCost();
    }

    fillSubMoney = realCost/100 * 22;
    return  foodCost + tableWareCost - redPacketCost - fillSubMoney;
}

好吧,依然乱的要命,不过setTakeOutBeanData()里面已经初见成效了,这里的错误现在先不管它。现在把getTakeOutFoodCost()的foodCost权责分开,把realCost的计算错误纠正:

第三步,分离getTakeOutFoodCost()的权责

public void payMoney(){
    int takeOutFoodCost = getTakeOutFoodCost();
    setTakeOutBeanData();
    //doSomething
}

public void setTakeOutBeanData(){
    takeOutBean.setFoodCost(foodCost);
    takeOutBean.setTableWareCost(tableWareCost);

    if(takeOutBean.getRedPacketCost()!=0){
        takeOutBean.setCostByRedPacket(1);
    }else{
        takeOutBean.setCostByRedPacket(0);
    }

    takeOutBean.setRealCost(realCost);
    takeOutBean.setFillSubMoney(fillSubMoney);
}

public double getTakeOutFoodCost(){
    double foodCost = 0;
    double tableWareCost = 0;
    double redPacketCost = 0;
    double deliveryCost = 0;
    double realCost = 0;//实际价格(不减)
    double fillSubMoney = 0;

    for(FoodBean foodBean:foodBeans){
        foodCost += foodBean.getCost();
    }

    tableWareCost = takeOutBean.getNumOfPeople() * takeOutBean.getSingleTableWareCost();

    if(takeOutBean.getRedPacketCost()!=0){
        redPacketCost = takeOutBean.getRedPacketCost(); 
    }

    if(takeOutBean.needDeliveryCost())
            deliveryCost =  foodBean.getDeliveryCost();
    realCost = foodCost + tableWareCost+deliveryCost +tableWareCost;

    fillSubMoney = realCost/100 * 22;

    return  foodCost + tableWareCost + deliveryCost - redPacketCost - fillSubMoney;
}

然后稍微整理一下,代码整齐了好多,注意返回的数据要加上送货费deliveryCost,实际上,红包价格是否为零对获取红包价格完全没影响不是吗?那么if(takeOutBean.getRedPacketCost()!=0){}的判断可以去掉了:

第四步,去除无效的判断:

public void payMoney(){
    int takeOutFoodCost = getTakeOutFoodCost();
    setTakeOutBeanData();
    //doSomething
}

public void setTakeOutBeanData(){
    takeOutBean.setFoodCost(foodCost);
    takeOutBean.setTableWareCost(tableWareCost);

    if(takeOutBean.getRedPacketCost()!=0){
        takeOutBean.setCostByRedPacket(1);
    }else{
        takeOutBean.setCostByRedPacket(0);
    }

    takeOutBean.setRealCost(realCost);
    takeOutBean.setFillSubMoney(fillSubMoney);
}

public double getTakeOutFoodCost(){
    double foodCost = 0;
    double tableWareCost = 0;
    double redPacketCost = 0;
    double deliveryCost = 0;
    double realCost = 0;//实际价格(不减)
    double fillSubMoney = 0;

    for(FoodBean foodBean:foodBeans){
        foodCost += foodBean.getCost();
    }

    tableWareCost = takeOutBean.getNumOfPeople() * takeOutBean.getSingleTableWareCost();

    redPacketCost = takeOutBean.getRedPacketCost(); 


    if(takeOutBean.needDeliveryCost())
            deliveryCost =  foodBean.getDeliveryCost();
    realCost = foodCost + tableWareCost+deliveryCost +tableWareCost;

    fillSubMoney = realCost/100 * 22;

    return  foodCost + tableWareCost + deliveryCost - redPacketCost - fillSubMoney;
}

然后,我们可以发现,每种价格都已经完美的分割开了,可以独立成函数了:

第五步,独立各种价格成函数

public void payMoney(){
    int takeOutFoodCost = getTakeOutFoodCost();
    setTakeOutBeanData();
    //doSomething
}

public double getTakeOutFoodCost(){
    return  getFoodCost()+ getTableWareCost()+ getDeliveryCost()- takeOutBean.getRedPacketCost()- getFillSubMoney();
}
public void setTakeOutBeanData(){
    takeOutBean.setFoodCost(foodCost);
    takeOutBean.setTableWareCost(tableWareCost);

    if(takeOutBean.getRedPacketCost()!=0){
        takeOutBean.setCostByRedPacket(1);
    }else{
        takeOutBean.setCostByRedPacket(0);
    }

    takeOutBean.setRealCost(realCost);
    takeOutBean.setFillSubMoney(fillSubMoney);
}



private double getFillSubMoney(){
    return getRealCost()/100 * 22;
}

public double getRealCost(){
    return getFoodCost() + getTableWareCost() + takeOutBean.getRedPacketCost() + getDeliveryCost();
}

public double getFoodCost(){
    double foodCost = 0;
    for(FoodBean foodBean:foodBeans){
        foodCost += foodBean.getCost();
    }
    return foodCost;
}

public double getTableWareCost(){
    return takeOutBean.getNumOfPeople() * takeOutBean.getSingleTableWareCost();
}

public double getDeliveryCost(){
    if(takeOutBean.needDeliveryCost())
        return foodBean.getDeliveryCost();
    return 0;
}

棒极了,非常整洁!所有的地方最多只有一层!此时可以发现,上面的setTakeOutBeanData()竟然很容易就可以改好了:

第五步,修改setTakeOutBeanData()

public void payMoney(){
    int takeOutFoodCost = getTakeOutFoodCost();
    setTakeOutBeanData();
    //doSomething
}

public void setTakeOutBeanData(){
    takeOutBean.setFoodCost(getFoodCost());
    takeOutBean.setTableWareCost(getTableWareCost());

    if(takeOutBean.getRedPacketCost()!=0){
        takeOutBean.setCostByRedPacket(1);
    }else{
        takeOutBean.setCostByRedPacket(0);
    }

    takeOutBean.setRealCost(getRealCost());
    takeOutBean.setFillSubMoney(getFillSubMoney());
}

public double getTakeOutFoodCost(){
    return  getFoodCost()+ getTableWareCost()+ getDeliveryCost()- takeOutBean.getRedPacketCost()- getFillSubMoney();
}

public double getRealCost(){
    return getFoodCost() + getTableWareCost() + takeOutBean.getRedPacketCost() + getDeliveryCost();
}

public double getFoodCost(){
    double foodCost = 0;
    for(FoodBean foodBean:foodBeans){
        foodCost += foodBean.getCost();
    }
    return foodCost;
}

public double getTableWareCost(){
    return takeOutBean.getNumOfPeople() * takeOutBean.getSingleTableWareCost();
}

public double getDeliveryCost(){
    if(takeOutBean.needDeliveryCost())
        return foodBean.getDeliveryCost();
    return 0;
}


public double getFillSubMoney(){
    return getRealCost()/100 * 22;
}

setTakeOutBeanData()里面有个if…else,把这个放出来效果更好:

第六步,抽离设置里面的if…else

public void payMoney(){
    int takeOutFoodCost = getTakeOutFoodCost();
    setTakeOutBeanData();
    //doSomething
}

public void setTakeOutBeanData(){
    takeOutBean.setFoodCost(getFoodCost());
    takeOutBean.setTableWareCost(getTableWareCost());
    takeOutBean.setCostByRedPacket(getTypeByRedPacketCost());
    takeOutBean.setRealCost(getRealCost());
    takeOutBean.setFillSubMoney(getFillSubMoney());
}

public int getTypeByRedPacketCost(){
    return takeOutBean.getRedPacketCost()==0?0:1;
}

public double getTakeOutFoodCost(){
    return  getFoodCost()+ getTableWareCost()+ getDeliveryCost()- takeOutBean.getRedPacketCost()- getFillSubMoney();
}

public double getRealCost(){
    return getFoodCost() + getTableWareCost() + takeOutBean.getRedPacketCost() + getDeliveryCost();
}

public double getFoodCost(){
    double foodCost = 0;
    for(FoodBean foodBean:foodBeans){
        foodCost += foodBean.getCost();
    }
    return foodCost;
}

public double getTableWareCost(){
    return takeOutBean.getNumOfPeople() * takeOutBean.getSingleTableWareCost();
}

public double getDeliveryCost(){
    if(takeOutBean.needDeliveryCost())
        return  foodBean.getDeliveryCost();
    return 0;
}


public double getFillSubMoney(){
    return getRealCost()/100 * 22;
}

第七步,为了阅读方便,我们调换一下各个函数的顺序:

public void payMoney(){
    int takeOutFoodCost = getTakeOutFoodCost();
    setTakeOutBeanData();
    //doSomething
}


public double getTakeOutFoodCost(){
    return  getFoodCost()+ getTableWareCost()+ getDeliveryCost()- takeOutBean.getRedPacketCost()- getFillSubMoney();
}

public void setTakeOutBeanData(){
    takeOutBean.setFoodCost(getFoodCost());
    takeOutBean.setTableWareCost(getTableWareCost());
    takeOutBean.setCostByRedPacket(getTypeByRedPacketCost());
    takeOutBean.setRealCost(getRealCost());
    takeOutBean.setFillSubMoney(getFillSubMoney());
}

public double getFoodCost(){
    double foodCost = 0;
    for(FoodBean foodBean:foodBeans){
        foodCost += foodBean.getCost();
    }
    return foodCost;
}


public double getTableWareCost(){
    return takeOutBean.getNumOfPeople() * takeOutBean.getSingleTableWareCost();
}


public double getDeliveryCost(){
    if(takeOutBean.needDeliveryCost())
            return  foodBean.getDeliveryCost();
    return 0;
}

public double getFillSubMoney(){
    return getRealCost()/100 * 22;
}

public double getRealCost(){
    return getFoodCost() + getTableWareCost() + takeOutBean.getRedPacketCost() + getDeliveryCost();
}


public int getTypeByRedPacketCost(){
    return takeOutBean.getRedPacketCost()==0?0:1;
}

现在这段代码终于“合格”了,看计算收费的代码:

public double getTakeOutFoodCost(){
    return  getFoodCost()+ getTableWareCost()+ getDeliveryCost()- takeOutBean.getRedPacketCost()- getFillSubMoney();
}

马上知道是收费=食物费+餐具费+送货费-红包-满减,然后如果后期有修改,改需要的地方就可以了。意识到了吗?实际上,只要我们把贪心的权责分开,然后就能够把各个分离出的部分写成函数(方法),我们的代码量实际上并没有增加多少,但是逻辑上更清晰了,各变量的耦合都降低,易读性和可扩展性都有显著的提升。

内容概要:本文介绍了基于Matlab代码实现的【EI复现】考虑网络动态重构的分布式电源选址定容优化方法,重点研究在电力系统中结合网络动态重构技术进行分布式电源(如光伏、风电等)的最佳位置选择与容量配置的双层优化模型。该方法综合考虑配电网结构变化与电源布局之间的相互影响,通过优化算法实现系统损耗最小、电压稳定性提升及可再生能源消纳能力增强等多重目标。文中提供了完整的Matlab仿真代码与案例验证,便于复现实验结果并拓展应用于微网、储能配置与配电系统重构等相关领域。; 适合人群:电力系统、电气工程及其自动化等相关专业的研究生、科研人员及从事新能源规划与电网优化工作的工程师;具备一定Matlab编程基础和优化理论背景者更佳。; 使用场景及目标:①用于科研论文复现,特别是EI/SCI级别关于分布式能源优化配置的研究;②支【EI复现】考虑网络动态重构的分布式电源选址定容优化方法(Matlab代码实现)撑毕业设计、课题项目中的电源选址定容建模与仿真;③辅助实际电网规划中对分布式发电接入方案的评估与决策; 阅读建议:建议结合提供的网盘资源下载完整代码与工具包(如YALMIP),按照文档目录顺序逐步学习,注重模型构建思路与代码实现细节的对应关系,并尝试在不同测试系统上调试与扩展功能。
本系统采用SpringBoot与Vue技术架构,实现了完整的影院票务管理解决方案,包含后台数据库及套可执行代码。该系统在高等院校计算机专业毕业设计评审中获得优异评价,特别适用于正在进行毕业课题研究的学生群体,以及需要提升项目实践能力的开发者。同时也可作为课程结业作业或学期综合训练项目使用。 系统提供完整的技术文档和经过面测试的源代码,所有功能模块均通过多轮调试验证,保证系统稳定性和可执行性。该解决方案可直接应用于毕业设计答辩环节,其技术架构符合现代企业级开发规范,采用前后端分离模式,后端基于SpringBoot框架实现业务逻辑和数据处理,前端通过Vue.js构建用户交互界面。 系统核心功能涵盖影院管理、影片排期、座位预定、票务销售、用户管理等模块,实现了从影片上架到票务核销的完整业务流程。数据库设计遵循第三范式原则,确保数据一致性和完整性。代码结构采用分层架构设计,包含控制器层、服务层、数据访问层等标准组件,便于后续功能扩展和维护。 该项目不仅提供了可直接部署运行的完整程序,还包含详细的技术实现文档,帮助开发者深入理解系统架构设计理念和具体实现细节。对于计算机专业学生而言,通过研究该项目可以掌握企业级应用开发的流程,包括需求分析、技术选型、系统设计和测试部署等关键环节。 资源来源于网络分享,仅用于学习交流使用,请勿用于商业,如有侵权请联系我删除!
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值