> "JG" == Jenn G writes:
JG> On Tue, Aug 11, 2009 at 2:33 PM, Uri Guttman wrote:
>>> "JG" == Jenn G writes:
>>
>> JG> When I create a package, and call its methods by both object way and
>> JG> function (exported) way, how to avoid the conflict in arguments
>> JG> passing
On Tue, Aug 11, 2009 at 05:45, Jenn G. wrote:
> On Tue, Aug 11, 2009 at 2:33 PM, Uri Guttman wrote:
>>> "JG" == Jenn G writes:
>>
>> JG> When I create a package, and call its methods by both object way and
>> JG> function (exported) way, how to avoid the conflict in arguments
>> JG> passing
On Tue, Aug 11, 2009 at 2:33 PM, Uri Guttman wrote:
>> "JG" == Jenn G writes:
>
> JG> When I create a package, and call its methods by both object way and
> JG> function (exported) way, how to avoid the conflict in arguments
> JG> passing?
>
> why are you trying to do OO and procedural call
On Tue, Aug 11, 2009 at 02:14, Jenn G. wrote:
> Hello,
>
> When I create a package, and call its methods by both object way and
> function (exported) way, how to avoid the conflict in arguments
> passing?
snip
Short answer: don't do that.
Medium answer:
Mixing procedural and OO style in the same
> "JG" == Jenn G writes:
JG> When I create a package, and call its methods by both object way and
JG> function (exported) way, how to avoid the conflict in arguments
JG> passing?
why are you trying to do OO and procedural calls on the same subs? it
makes no sense. how will a procedural
