fail fast fail early - Page 175

Static code analysis tool for detecting uncaught exceptions in a C++ code before compilation?

- by Séverin

I'm looking for such a tool to be able to check fast if I catch all the exceptions I generate myself. Thanks!

C# memory allocation

- by user279691

Does using operator new in c# might fail (if it requires a large memory)? -Solved- And how to discover it? -Solved- What other failures new operator might throw? Thanks

How to manipulate file paths intelligently in .Net 3.5?

Scenario: I am maintaining a function which helps with an install - copies files from PathPart1/pending_install/PathPart2/fileName to PathPart1/PathPart2/fileName. It seems that String.Replace() and Path.Combine() do not play well together. The code is below. I added this section: // The behavior of Path.Combine is weird. See: // http://stackoverflow.com/questions/53102/why-does-path-combine-not-properly-concatenate-filenames-that-start-with-path-dir while (strDestFile.StartsWith(@"\")) { strDestFile = strDestFile.Substring(1); // Remove any leading backslashes } Debug.Assert(!Path.IsPathRooted(strDestFile), "This will make the Path.Combine(,) fail)."); in order to take care of a bug (code is sensitive to a constant @"pending_install\" vs @"pending_install" which I did not like and changed (long story, but there was a good opportunity for constant reuse). Now the whole function: //You want to uncompress only the files downloaded. Not every file in the dest directory. private void UncompressFiles() { string strSrcDir = _application.Client.TempDir; ArrayList arrFiles = new ArrayList(); GetAllCompressedFiles(ref arrFiles, strSrcDir); IEnumerator enumer = arrFiles.GetEnumerator(); while (enumer.MoveNext()) { string strDestFile = enumer.Current.ToString().Replace(_application.Client.TempDir, String.Empty); // The behavior of Path.Combine is weird. See: // http://stackoverflow.com/questions/53102/why-does-path-combine-not-properly-concatenate-filenames-that-start-with-path-dir while (strDestFile.StartsWith(@"\"")) { strDestFile = strDestFile.Substring(1); // Remove any leading backslashes } Debug.Assert(!Path.IsPathRooted(strDestFile), "This will make the Path.Combine(,) fail)."); strDestFile = Path.Combine(_application.Client.BaseDir, strDestFile); strDestFile = strDestFile.Replace(Path.GetExtension(strDestFile), String.Empty); ZSharpLib.ZipExtractor.ExtractZip(enumer.Current.ToString(), strDestFile); FileUtility.DeleteFile(enumer.Current.ToString()); } } Please do not laugh at the use of ArrayList and the way it is being iterated - it was pioneered by a C++ coder during a .Net 1.1 era. I will change it. What I am interested in: what is a better way of replacing PathPart1/pending_install/PathPart2/fileName with PathPart1/PathPart2/fileName within the current code. Note that _application.Client.TempDir is just _application.Client.BaseDir + @"\pending_install". While there are many ways to improve the code, I am mainly concerned with the part which has to do with String.Replace(...) and Path.Combine(,). I do not want to make changes outside of this function. I wish Path.Combine(,) took an optional bool flag, but it does not. So ... given my constraints, how can I rework this so that it starts to suck less?

Search Results

Search found 11913 results on 477 pages for 'fail fast fail early'.

Page 175/477 | < Previous Page | 171 172 173 174 175 176 177 178 179 180 181 182 | Next Page >

- by Séverin

- by user279691

- by Hamish Grubijan

- by Beck

- by Ramsey

- by Zerotoinfinite

- by Timj

- by knappy

- by lanqy

- by fish

- by dayscott

- by Eduardo

- by pm_2

- by Jeremy Stein

- by Alexey Romanov

- by Ole Jak

- by stacker

- by clyfe

- by npinti

- by Manuel Darveau

- by Jalfp

- by ensnare

- by dontWatchMyProfile

- by user293120

- by carter-boater

< Previous Page | 171 172 173 174 175 176 177 178 179 180 181 182 | Next Page >