parameter-passing

So, here's a small problem I'm facing right now -> I'm trying to write a function that will accept a char* message and a variable number of arguments. My function will modify the message a little, and then It'll call printf with the message and given parameters. Essentialy, I'm trying to write something like that: void modifyAndPrintMessage(char* message,...){ char* newMessage; //copy message. //Here I'm modifying the newMessage to be printed,and then I'd like to print it. //passed args won't be changed in any way. printf(newMessage,...); //Of course, this won't work. Any ideas? fflush(stdout)

Considering that in the Ruby programming language everything is said to be an Object, I safely assumed that passing arguments to methods are done by reference . However this little example below puzzles me: $string = "String" def changer(s) s = 1 end changer($string) puts $string.class String => nil As you can see the original Object wasn't modified, I wish to know why , and also, how could I accomplish the desired behavior ie. Getting the method to actually change the object referenced by its argument. The way Ruby works is a combination of pass by value and pass by reference. In fact, Ruby

If I don't know how many arguments a function will be passed, I could write the function using argument packing: def add(factor, *nums): """Add numbers and multiply by factor.""" return sum(nums) * factor Alternatively, I could avoid argument packing by passing a list of numbers as the argument: def add(factor, nums): """Add numbers and multiply by factor. :type factor: int :type nums: list of int """ return sum(nums) * factor Is there an advantage to using argument packing *args over passing a list of numbers? Or are there situations where one is more appropriate? *args / **kwargs has its

Note: A summary of this question has since been posted at the PowerShell GitHub repository , since superseded by this more comprehensive issue . Arguments passed to a command in PowerShell are parsed in argument mode (as opposed to expression mode - see Get-Help about_Parsing ). Conveniently, (double-)quoting arguments that do not contain whitespace or metacharacters is usually optional , even when these arguments involve variable references (e.g. $HOME\sub ) or subexpressions (e.g., version=$($PsVersionTable.PsVersion) . For the most part, such unquoted arguments are treated as if they were

I am designing a simple Data Access Object for my Java application. I have a few classes (records) that represents a single row in tables like User and Fruit . I would like to have a single method for getting all records of a specific type. For the moment I have it like this: public List<User> getAllUsers() { ... } public List<Fruit> getAllFruits() { ... } .... But I would like to have a single polymorphic method like this (wrong): public List<T> getAllRecords(Class<T> type) { if(type instanceof User) { // Use JDBC and SQL SELECT * FROM user } else if(type instanceof Fruit) { // Use JDBC and

I'm looking for the C# equivalent of Java's final . Does it exist? Does C# have anything like the following: public Foo(final int bar); In the above example, bar is a read only variable and cannot be changed by Foo() . Is there any way to do this in C#? For instance, maybe I have a long method that will be working with x , y , and z coordinates of some object (ints). I want to be absolutely certain that the function doesn't alter these values in any way, thereby corrupting the data. Thus, I would like to declare them readonly. public Foo(int x, int y, int z) { // do stuff x++; // oops. This

I have a script that reads a configuration file that results in a set of name value pairs that I would like to pass as arguments to a function in a second PowerShell script. I do not know what parameters will be placed in this configuration file at design time, so right at the point where I need to invoke this second PowerShell script, I basically just have one variable that has the path to this second script, and a second variable that is an array of arguments to pass to the script identified in the path variable. So the variable containing the path to the second script ($scriptPath), might