> I was hoping to get us something that was guaranteed to hold an integer, no > matter what it was, so you could do something like: > > struct thingie { > UV type; > INT my_int; > } What is the purpose of doing this? The SV is guaranteed to hold anything. Why we need a type that can hold any integer, and a type that can hold any float. The struct/union solution does not provide much type safety. How can I tell which member is valid without external knowledge. I don't think we really need this type, using SV instead. Hong
- RE: Questions about PDD 4: Internal dat... NeonEdge
- Re: Questions about PDD 4: Interna... Hong Zhang
- Re: Questions about PDD 4: Int... Dan Sugalski
- Re: PDD 4: Internal data types Andy Dougherty
- Re: PDD 4: Internal data types Dan Sugalski
- Re: PDD 4: Internal data types Nicholas Clark
- Re: PDD 4: Internal data types Dan Sugalski
- Re: PDD 4: Internal data types Hong Zhang
- Re: PDD 4: Internal data types Jarkko Hietaniemi
- Re: PDD 4: Internal data types Dan Sugalski
- Re: PDD 4: Internal data types Hong Zhang
- Re: PDD 4: Internal data types Dan Sugalski
- Re: PDD 4: Internal data types Dan Sugalski
- Re: PDD 4: Internal data types Uri Guttman
- PDD X: Perl API conventions Paolo Molaro
- Re: PDD X: Perl API conventions Damien Neil
- Re: PDD X: Perl API conventions Stephen P. Potter
- Re: PDD X: Perl API conventions Dan Sugalski
- Re: PDD X: Perl API conventions Paolo Molaro
- Re: PDD X: Perl API conventions Damien Neil
- Re: PDD 4: Internal data types Hong Zhang