One of the things you could imagine is just try it on and input, see how long it takes.
你们想出来的方法只是可能就是通过,输入来试试,看运行时间会有多长。
So before we use printf, a function, and we passed in one input and input henceforth we're gonna call arguments or parameters.
我们在使用printf函数时,先放进去一个输入,之后的输入我们就要,调用参数了。
And by that, I mean, not how much memory do I need to store the size of the input, it's really how much internal memory do I use up as I go through the computation?
需要占用多少内存,我意思并不是,存储输入需要多少内存,而是当我完成这个?
So, this is what goes on in an electrolysis cell, and it works thanks to input energy from a power supply shown here.
所以,这是在一个电化学电池中发生的,它是靠输入的能量工作的,从和这个类似的电源输出的能量。
So the body breaks and no longer is able to give input up to the soul.
由于肉体死亡了,它将不再给灵魂输入指令
q1 The heat input is just q1, Q and we'll define that as capital Q.
输入的热是,我们把它定义为大写的。
I could generalize this pretty nicely. Imagine the same kind of idea where I want to simply say I want to take input of anything and try and see how to make sure I get the right kind of thing. I want to make it polymorphic.
对吧,我试着输入浮点数,我能更好的一般化它,想象下类似的想法,我需要输入些什么,然后看看输入的是否正确,我想使他更多元化些。
bug What I typically do is I start with the input that provoked the problem, and I keep making it smaller and smaller.
我这里做的就是从引起,出现的输入开始,然后将输入,一步步的缩小规模。
Even though my statement said enter a number, in particular, raw input here simply takes in a set of characters and treats it as a string.
即使我的陈述说的是应该输入一个数字,实际上,这里的原始输入会被当做一个字符,的集合来提取并被当做一个字符串来对待。
I'm going to run through a loop, and I'm going to request some input, which I'm going to read in with raw input.
我要运行一个循环,我需要一些输入,需要读入一些原始的输入。
> Computer our input, memory control, arithmetic, and logic and output.
>,【记录的演示】计算我们的输入,内存控制,算法,逻辑和输出。
So we can provide any form of input here and the program will just keep working.
为您提供各种形式的输入,程序也一直工作。
Which is a way of reminding you that I need to think as I write the code about what are my expectations from the input, and how might I enforce them.
通过这个我在提醒大家,在写代码的时候,要搞清楚对输入的期望,并思考下如何执行这些期望。
The only thing I've done in this part of the program, now I'm going to go and read the code, is I've gotten the user to input a bunch of data.
现在我去读读这里的代码,是我会让用户输入一些数据,然后根据用户输入的数据。
If I decide there's a better way to get input, and there is, then I can make it to change what I don't have to change the code that uses the input.
如果我觉得有更好的获取输入的方法,我可以直接改去用这种方式,而不用更改使用了,输入处的代码。
We've been using strings thus far to get input from user and store it in variables.
迄今为止,我们用字符串来接受用户的输入,然后存储在变量里。
What does it expect as input, and any other information I want to pass on.
但是如果我去做了,我将要说明这个函数是干什么的。
I'm going to have it take in as input how many legs I got, how many heads do I have, and I just want to write a little loop.
这就是解决问题的思路,我将要输入我有多少条腿,以及我有多少只头。
And its purpose in life is to maybe take input and maybe produce output.
它的唯一目的是可能是获得输入,可能是输出东西。
So you try and find a smaller input that bug will produce the problem.
你应该尝试着用规模小一点的输入,去重现这个。
So one of the things I want you to notice here is that testing and debugging are not the same thing. When we test, we compare an input output pair to a specification.
这里我想大家注意的一件事,就是测试和调试是不同的两件事情,我们测试的时候,我们把输入输出,跟程序的规格说明书对比下。
But when you start writing programs, especially when we get to web-based stuff where you want -- to check the user's input -- is it valid, is it an email address, -- and all these different scenarios -- it's actually often useful to be able to just enumerate them or rattle them off using this switching construct instead.
但是当你看是写程序时,特别是当我们,使用基于网络的东西,你想要,检查用户的输入-,它是合法的吗?它是不是一个电子邮箱地址?,所有的这些场景-,实际上它常常是有用的,当你用枚举结构列举它们,或者用它来快速地来说出它们。
And yet notice that the function itself, it takes no input.
请注意函数本身,它没有输入。
Suppose instead, I want a machine that can take a recipe, the description of a sequence of steps, take that as its input, and then that machine will now act like what is described in that recipe.
假设换成这个,我想要一台可以安装描述,一系列步骤的结果的方法的机器,把那个当做输入设备,然后那台机器可以像方法中,描述的那样运行了。
And given those types of input, will get back output.
然后鉴于输入类型返回结果输出。
And often there's human input.
人们得输入一些东西。
The format is the same. I'm going to ask for some input, and then I am going to use that procedure to check, is this the right type of value. And I'm trying to use that to do the coercion if you like. Same thing if it works, I'm going to skip that, if it not, it's going to throw the exception.
格式是一样的,我需要一些输入,然后我要用一个过程来检查,是否是正确的值,然后你就可以做强制转换了,如果能运行,那是一样的,我打算跳过这段,如果不正确,那就会抛出一个异常。
This is exactly where I don't really know the details, but I take it it's something like: because of whatever the original input was, eventually the blood's no longer circulating and oxygen isn't making its way around the body.
事实上我对这方面不是很了解,我只能认为是,不论最初的死亡原因是什么,最后血液不再流动,氧气不能输送到全身
That's the question we're going to try and address. If we can do this, this is good, because first of all, it removes any questions about what machine I'm running on, it's talking about fundamentally, how hard is this problem, and the second thing is, it is going to do it specifically in terms of the input. Which is one of the things that I was worried about.
这是一个我们接下来要去,尝试和解决的问题,如果我们能做到的话会很不错,因为首先,它解决了结果可能和我,运行的计算机有关系的问题,因为这从根本了告诉了,我们这个问题的复杂度,第二件事情,就是这种方法可以依据输入的大小来计算,而这正是我最担心的地方。
应用推荐