Saturday, March 21, 2020

Vincent essays

Vincent essays V When I first of this assignment I had a tuff time, trying to find out who or what I was going top write on. I consider myself some what of an artist. But I don't draw skecthes or paint masterpeices. Im a writer, Im like most other artsist that paint. instead of seeing and images from my head and paint them on my canvis. I take my emotions, put them in words and in my own type of canvis creating my version of a materpeice. I wanted to pick an artist that was like me in a way, one that I could mostly relate to. When I was in seventh grade, I took french 1. We covered a lot of there culturethe majority of it was. We came across a mans life that to me will always be a legacy.His name was Vincent vanGogh. Vincent van Gogh was seen as a failure in his lifetime which lead to various mental disorders and ultimately suicide, but today he is viewed as the foremost representative of postimpressionist art. Unable to conform to normal life, Vincent turned to art to passionately express hi s feelings. His style of choppy brush strokes of amazing colors was looked down upon by other artist of his time but with support from his brother, Theo, Vincent lived his dream of becoming an artist. Although he enjoyed painting, the intense feeling of failure and rejection by women, took a toll on Vincent. He went through long bouts of depression, which led to his suicide. Today, Van Gogh is seen as one of the most achieved and inspirational artists of all time. Vincent van Gogh was born on March 30, 1853 in North Brafant, Holland. He was the son of Theodorus van Gogh, an evangelical Calvinist, and Anna Cornelia Carbentus. He was the second son named Vincent, the first died an infant. This always made Vincent feel like a replacement son for his parents, like there was a sence of guilt with him. As a child Vincent was shy, and preferred to be alone. He liked the outdoors and admired its beauty, which he portrayed is his paintings later in l...

Wednesday, March 4, 2020

The try-catch-finally Blocks in Java

The try-catch-finally Blocks in Java To make a Java program as robust as possible it needs to be able to handle exceptions. The compiler does its part by not allowing you to compile a program until it is syntactically correct and can also point out checked exceptions that must be handled. But the exceptions that are likely to cause the most headaches are the ones that appear once the program is running. To help handle these exceptions the Java language provides the try-catch-finally blocks. The try Block The tryblock encases any statements that might cause an exception to occur. For example, if you are reading data from a file using the FileReader class, its expected that you handle the IOExceptions associated with using a FileReader object, for example,FileNotFoundExceptionand IOException. To ensure this happens, you can place the statements that deal with creating and using the FileReader object inside a try block:However, the code is incomplete because, in order for the exception to be handled, we need a place for it to be caught. This happens in the catch block.The catch Block The catch block(s)  provide a place to handle the exception thrown by the statements within a try block. The catch block is defined directly after the try block. It must specify the type of exception it is handling. For example, the FileReader object defined in the code above is capable of throwing a FileNotFoundException or an IOException. We can specify two catch blocks to handle both of those exceptions:In the FileNotFoundExceptioncatchblock we could place code to ask the user to find the file for us and then try to read the file again. In the IOException catch block, we might just pass on the I/O error to the user and ask them to try something else. Either way, we have provided a way for the program to catch an exception and handle it in a controlled manner.In Java SE 7, it became possible to handled multiple exceptions in one catch block. If the code we wanted to place in the two catch blocks above was exactly the same we could write the code like this instead:In order to do a bit of housekeeping as far as resources go, we can add a finally block. After all, we want to release the file we have been reading from once we are finished. The finally Block The statements in the finally block are always executed. This is useful to clean up resources in the event of the try block executing without an exception and in the cases when there is an exception. In both eventualities, we can close the file we have been using.   The finally block appears directly after the last catch block: