Reasonable to expect it, yes -- but whether or not this rises to the

level of being a "requirement in the spec" may be a different matter.

I could envision the possibility that some otherwise-very-capa­ble

Perl 6 implementation might be better served by having such checks

performed at runtime (they have to be done there also) and leaving

compile-time checking as an optimization. I suspect this is what

Pugs did. Or an implementation might not have a clear-cut notion

of "compile time".

So, as long as the assignment is properly prevented, I think that

may be sufficient. (If the language designers decide otherwise,

that's okay with me too. ­

sub bar ($x)

{

$x = 3; # error, $x is readonly

foo($x); # error, could hit rw Str

}

I wrote a complete treatment of Inf support.

Please take a look at "24.26 Infinite" on pages 116-119, and

"3.11.3 Infinities" on pages 26-27.

Coming back to how C++ handles static overloading. How is

the sort order of (int *), (int &), (int), (const int *),

(const int &), (const int), (int * const) and (const int * const)?

I'm too lazy to look up the details, sorry.

I am creating a simple tool that will query one table and retrieve the data. Then this tool will turn the data into insert statements.

I was wondering if there was a way to retrieve the table name from the statement handle?

Similar to print "SQL statement contains $sth->{NUM_OF_FIELD­S} columns\n";

but like this

print "SQL statement table name is $sth->{TABLENAME} \n";

Joseph Lamb

___________________­____________________­____________________­____________________­_____

Be a better friend, newshound, and

know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo­.com/;_ylt=Ahu06i62s­R8HDtDypao8Wcj9tAcJ

BTW, what is a flack?

On Friday 02 May 2008 07:08:21 John M. Dlugosz wrote:

All classes imply the existence of a role of the same name.

-- c

To do multi method dispatch, you want to select the method that best

matches the parameters in the call. One way to do that is to define a

measure for distances between types and they use the method that's at

the minimum distance. One simple measure is that a type is distance 0

from itself and distance 1 from it's immediate super-types, distance 2

from the immediate super-types of it's immediate super-types, etc.

When dispatching over a single parameter picking the method at the

minimum distance is the usual most specific type match. But when you

want to do multi-method dispatch, you need some rule to combine the

various distances of the individual parameters into a single measure

value, then pick the method at the minimum distance by that combined

measure. "Manhattan Distance" or "Taxicab Distance" is the rule that

the combined distance is just the simple unweighted sum of the

individual parameter distances. The is named after the fact that a

taxi must follow the streets and to go 3 block north and 4 blocks west

it must travel 7 blocks not the 5 blocks of the euclidean distance.