Welcome to the Lounge

if (something)
  //old_command
  new_command;
else while (something)
{
  command 1;
  command 2;
//... more staff
}
//or..
if something for (...) if something one_liner;

M.D.V.

If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.

HttpClient client = new HttpClient();

using (Stream s = client.GetStreamAsync("http://www.test.com/large.json").Result)
using (StreamReader sr = new StreamReader(s))
using (JsonReader reader = new JsonTextReader(sr))
{
    JsonSerializer serializer = new JsonSerializer();
    // read the json from a stream
    // json size doesn't matter because only a small piece is read at a time from the HTTP request
    Person p = serializer.Deserialize<Person>(reader);
}

GuyThiebaut wrote:

code that is easier to debug is an idea that contradicts some of the more modern suggested coding patterns.

BryanFazekas wrote:

the author

{
    string data = inputStream.ReadToEnd();
    SomeClass myObj = JsonConvert.Deserialize<SomeClass>(data)
    var processed = Process(myObj);
    return JsonConvert.SerializeObject(processed);
}

{
#if DEBUG

    string data = inputStream.ReadToEnd();
    SomeClass myObj = JsonConvert.Deserialize<SomeClass>(data)
    var processed = Process(myObj);
    return JsonConvert.SerializeObject(processed);

#else

    return JsonConvert.SerializeObject(Process(JsonConvert.Deserialize<SomeClass>(inputStream.ReadToEnd())));

#endif
}

Product p = GetProduct(params);
return p;

Quote:

hey wouldn't mind generating segment:offset addresses that past the megabyte barrier, because it will roll over and map into the address space of the zeroth+ segment

Boolean summaryDescription = (super nasty Boolean expression with 4-8 components);

if (summaryDescription) {
   handleIt();
}