Re^6: More Macro work...out to export a definition to next-outer level?

[perl-diddler]

I don't know if you are still seeing replies, since I don't know how to get notified of replies to my replies other than to go find each thread I've written in and look for them, BUT, I'll try to clarify again. In my setup, I'm doing this (not copied from code, but written for demonstration, so if everything doesn't run, that's why):

package MyPackage;

our $global=0;

sub global {
  shift;
  $global=$_[0] if @_;
  $global;
}

sub instance {
  my $this=shift;
  if (@_) {
    $this->{instance}=$_[0];
    ++$global;
  }
  $instance;
}

sub new {
  my $package=shift;
  bless {},$package;
}

}

package main;

my $package = new MyPackage();

#main *doesn't* know what vars are per-class or which are per-instance
+.
# that's an implementation detail the caller doesn't know about
# so all calls are called through method calls.

$package->instance(1.7);
print "vars created = ",$package->global;
...
# reset MyPackage counter to globally reset counter for all users
# (not normal used; be available for better user control of counting..
+.
$package->global(0);
...

Is your complaint that I'm setting my global in a method call? That is intentional. In this situation, callers don't know the details of some variables -- whether they are per-class or per-instance. I am aware, that a caller could call an initializer function more than once. But in the use of the class, this would be an abnormal occurrence -- supported for development purposes, but not normally used.

Later, if I thought it was necessary, I could change the global definition and make some 'global_readonly', that only provides a 'get' function if I thought it necessary, but for now, I'm providing both.

I feel like we are playing 20 questions -- I keep trying to see if 'X' is what you are talking about. You keep saying 'wrong', 'its a mess'. But you don't clearly explain why its a mess. This isn't as helpful for me as your first explanation was on my prior question -- sorry.