it is important that you concentrate now on being able to commit your work in git. I give you below the reason for the error you got so far, that should be easy to correct.
On 09/02/2012 10:52 PM, Ricardo Aguirre wrote:
I already solved the 13)firstname.lastname@example.org <mailto:email@example.com-
My error was incredible stupid!
Now I have problems with git
last week I setup my global git configuration on my pc, I used this email:
now I'm getting this errors:
Ok, you're having hook problems. We have a hook that checks that the code you commit complies to GNAT style checks before allowing you to commit them. You can check these rules on your computer by compiling with switch -gnatyg. Many of these rules are so simple (indentation, spacing) that you can correct them in GPS by clicking on a small icon on the side that says "autofix". BTW, you can set up GPS so that it does the indentation automatically for you. I am joining the Ada Coding Style that we use at AdaCore.
at first it yields
RE : failed precondition from stacks.ads:39
Then I removed the old push precondition (not Is_Full(S))
now is running
I'm stocked with generics, I already read many chapters of ada book, but I'm doing something wrong, I hope I'll solve it during this weekend.
Now I see that stack example is really classic, and book talk about it in many chapters, actually I feel little embarrassed cause I'm having problems with really basic stuffs. However I'm working in.
To solve this point I have to ideas:
a) do not use anymore the array instead use a list, like the Cell example
b) Use a type base, and then all objects inserted on the array should be
subtype of this base type. Doing an analogy with java that each object
extends implicitly from Object Class.
When I tried to use your suggested postcondition
RE : failed postcondition from
stacks.ads:49 instantiated at main.adb:5/
I'm not pretty sure about the reason of this message.
Either your postcondition is wrong, or your implementation of Push is wrong. At least they do not match. Try inspecting values by debugging or printing to see which one it is.