argument-passing

I have a view controller which creates multiple subviews on top of it. All subviews and the view controller accept touches. How can i communicate the touch point information to all the subviews on the screen? Keep in mind that each subview covers the entire screen so after a few additions its a bit like pages in a book. That is, any subviews below the top subview can't be touched directly by the user. I have tried using [self.nextResponder touchesBegan:touches withEvent:event] however this only sends the touch information from the top subview to the superview bypassing all other subviews on

I want to know how to pass structures to another function and subsequently access that structure in the called function. I'm developing for the iPhone and the reason I'm using structs is so that I can eventually pass data as structs to a server being built in C. Here's the structure: struct userInfo{ NSString *firstName; NSString *lastName; NSString *username; NSString *email; NSString *ipAddress; double latitude; double longitude; }; Here I'm simply fetching some user inputed data along with some CoreLocation data and the iPhone's IP Address: - (IBAction)joinButton { struct userInfo localUser

How can one pass command line arguments via file association in Vista 64? I recently built a PC running Vista Ultimate 64-bit. I noticed several of the Perl scripts I transferred failed due to command-line arguments not being passed. As a simple test, I wrote the following (foo.pl): #!/usr/bin/perl -w use strict; my $num_args = $#ARGV + 1; print "${num_args} arguments read\n"; print "$^X\n" # to see what was being used Running "foo.pl 1 2 3" undesirably yielded: 0 arguments read C:\strawberry\perl\bin\perl.exe Running "perl foo.pl 1 2 3" expectedly yielded: 3 arguments read C:\strawberry\perl

In Python, we have the star (or "*" or "unpack") operator, that allows us to unpack a list for convenient use in passing positional arguments. For example: range(3, 6) args = [3, 6] # invokes range(3, 6) range(*args) In this particular example, it doesn't save much typing, since range only takes two arguments. But you can imagine that if there were more arguments to range , or if args was read from an input source, returned from another function, etc. then this could come in handy. In Scala, I haven't been able to find an equivalent. Consider the following commands run in a Scala interactive