On Oct 16, 2003, at 7:21 AM, Dan Sugalski wrote:
On Thu, 16 Oct 2003, Leopold Toetsch wrote:
Juergen Boemmels <[EMAIL PROTECTED]> wrote:
Leopold Toetsch <[EMAIL PROTECTED]> writes:
The IMCC_INFO does not need to be part of the interpreter.
I don't like to have global state variables around. I do
Melvin Smith <[EMAIL PROTECTED]> wrote:
> I don't like the idea of IMCC becoming so tightly coupled with the
> interpreter. I still wish to be able to build it standalone. Hopefully
> we can keep this in mind going forward.
IMCC_INFO is a macro, easily changable. But building it standalone would
At 10:21 AM 10/16/2003 -0400, Dan Sugalski wrote:
On Thu, 16 Oct 2003, Leopold Toetsch wrote:
> Juergen Boemmels <[EMAIL PROTECTED]> wrote:
> > Leopold Toetsch <[EMAIL PROTECTED]> writes:
>
> > The IMCC_INFO does not need to be part of the interpreter.
>
> I don't like to have global state variabl
On Thu, 16 Oct 2003, Leopold Toetsch wrote:
> Juergen Boemmels <[EMAIL PROTECTED]> wrote:
> > Leopold Toetsch <[EMAIL PROTECTED]> writes:
>
> > The IMCC_INFO does not need to be part of the interpreter.
>
> I don't like to have global state variables around. I don't know yet,
> what happens if 2 i
Juergen Boemmels <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch <[EMAIL PROTECTED]> writes:
> The IMCC_INFO does not need to be part of the interpreter.
I don't like to have global state variables around. I don't know yet,
what happens if 2 interpreter threads both do eval()...
>> It will be repla
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> JüRgen" "BöMmels <[EMAIL PROTECTED]> wrote:
>
> > There are still some things to do:
> > - a global hash is still not totally right. It should be moved to the
> > interpreter structure
>
> As Dan already outlined, macros should have some limited sc
JüRgen" "BöMmels <[EMAIL PROTECTED]> wrote:
> There are still some things to do:
> - a global hash is still not totally right. It should be moved to the
> interpreter structure
As Dan already outlined, macros should have some limited scope, probably
per file. So currently the hash has to be cle
On Wed, 15 Oct 2003, Jürgen Bömmels wrote:
> There are still some things to do:
> - a global hash is still not totally right. It should be moved to the
> interpreter structure
Nope. The macro hash should be per-compilation-unit, not global in any
way. It should go away when compilation is done.
# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #24224]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=24224 >
Hi,
Back in Feburary, when I hacked up macro support for IMCC I
implemented the macro
