out

this code works fine on emulator, but on real device it gives java.net.SocketException :the operation timed out ive got a php script running on my xampp server. package com.example.new1; import java.io.BufferedReader; import java.io.InputStreamReader; import java.net.HttpURLConnection; import java.net.URL; import android.os.AsyncTask; import android.os.Bundle; import android.app.Activity; import android.view.Menu; import android.view.View; import android.widget.TextView; public class MainActivity extends Activity { TextView tx; StringBuilder stringBuilder; @Override protected void onCreate

I get 48 when I input 0 to a ReadLine(). Is this a bug? class Program { static void Main(string[] args) { string name; int age; readPerson(out name, out age); } static void readPerson(out string name, out int age) { Console.Write("Enter name: "); name = Console.ReadLine(); Console.Write("Enter age: "); age = Console.Read(); Console.WriteLine("Name: {0}; Age: {1}", name, age.ToString()); } } According to the MSDN documentation, the Console.Read method returns: The next character from the input stream, or negative one (-1) if there are currently no more characters to be read. So, really what you

Do out parameters in C# have any performance implications I should know about? (Like exceptions) I mean, is it a good idea to have a method with an out parameter in a loop that will run a couple of million times a second? I know it's ugly but I am using it the same way as Int32.TryParse is using them - returning a bool to tell if some validation was successful and having an out parameter containing some additional data if it was successful. I doubt that you'll find any significant performance penalty to using an out parameter. You've got to get information back to the caller somehow or other -

In C# PInvoke, how do I pass a string buffer so that the C DLL fills it and returns? What will be the PInvoke declaration? The C function declaration is int GetData(char* data, int buflength); In C#, I have declared it as [DllImport(DllName)] static extern Int32 GetData([MarshalAs(UnmanagedType.LPStr)]StringBuilder receiveddata, Int32 buflen); Is it correct? I'm passing the StringBuilder variable like this int bufferLength = 32; StringBuilder data = new StringBuilder(bufferLength); int result = GetData(data, bufferLength); I would like to know is it correct or not? Thanks I believe it's

This question already has an answer here: Func<T> with out parameter 4 answers Func<a, out b, bool> , just don't compile, how to declare that i want the second parameter be an out one? I want to use it like this: public class Foo() { public Func<a, out b, bool> DetectMethod; } Andrew Bezzub Actually, Func is just a simple delegate declared in the .NET Framework. Actually, there are several Func delegates declared there: delegate TResult Func<TResult>() delegate TResult Func<T, TResult>(T obj) delegate TResult Func<T1, T2, TResult>(T1 obj1, T2 obj2) delegate TResult Func<T1, T2, T3, TResult>(T1

I'm making a call: myResult = MakeMyCall(inputParams, out messages); but I don't actually care about the messages. If it was an input parameter I didn't care about I'd just pass in a null. If it was the return I didn't care about I'd just leave it off. Is there a way to do something similar with an out, or do I need to declare a variable that I will then ignore? Starting with C# 7.0, it is possible to avoid predeclaring out parameters as well as ignoring them. public void PrintCoordinates(Point p) { p.GetCoordinates(out int x, out int y); WriteLine($"({x}, {y})"); } public void

When a C# function has an output parameter, you make that clear as follows: private void f(out OutputParameterClass outputParameter); This states that the parameter does not have to be initialized when the function is called. However, when calling this function, you have to repeat the out keyword : f(out outputParameter); I am wondering what this is good for. Why is it necessary to repeat part of the function specification? Does anyone know? It means you know what you're doing - that you're acknowledging it's an out parameter. Do you really want the utterly different behaviour to happen