Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108090
MIME-Version: 1.0
References: <5e0d723f.1c69fb81.e2ae8.24e2SMTPIN_ADDED_MISSING@mx.google.com>
 <74F2DBFC-E63C-428C-A37F-2D0CEE15AD0F@newclarity.net> <DM5PR07MB30676FC66DA036895D5E3554F9200@DM5PR07MB3067.namprd07.prod.outlook.com>
 <CD014984-715D-49C5-9A90-66C0A11F9818@newclarity.net> <c40a96fe-8929-4b44-98bd-3370a12ec516@www.fastmail.com>
 <D56361F6-8B11-4363-908D-962F683936BF@newclarity.net> <b32edf0c-451d-2281-8036-0b631a3c7a6f@gmail.com>
 <CD3AFCD7-EF2F-46C7-90D3-3A83A1D8836C@newclarity.net> <53556dfb-44ce-f902-204c-9a7da9484a61@gmail.com>
 <65567C7C-CF0F-4562-8943-F1F302134B07@newclarity.net> <f9e2f739-4964-b259-d9e5-4aeec938c54b@gmail.com>
 <F48FF1DC-5DE9-4C30-8BCF-C17A1877AF37@newclarity.net> <6f20bda1-eff6-631d-915f-d6bb149ee666@gmail.com>
 <93BA4B49-9D9A-4A41-83B3-8EC2564A70BF@newclarity.net> <CALKiJKoi7AH0ypkQN8p7S8jeO2M1qNnyMUfdDM+w4iLwhskskg@mail.gmail.com>
 <A819AFCE-875E-432E-9D87-EC4D970DF1DD@newclarity.net> <CALKiJKqjXBr4jB7oh0gVPc9Q8ABgZaQ-=MzJb8Ry544Orr9oBA@mail.gmail.com>
 <CBAAE45D-E957-4033-B93C-5D7995C7209E@newclarity.net> <CALKiJKqv_Q7vmPaOgzSzytZ5uH8jL7oFbbiLTNXpHTrh-mc-Bg@mail.gmail.com>
 <106024FC-F36B-4E4E-9383-6430025A8D60@newclarity.net>
In-Reply-To: <106024FC-F36B-4E4E-9383-6430025A8D60@newclarity.net>
Date: Fri, 10 Jan 2020 15:11:47 +0000
Message-ID: <CAMuFt-7N7rJrUX_ArLCko_OhB=W6p1Q0YDe2d-Zk_OAk_VtShw@mail.gmail.com>
To: Mike Schinkel <mike@newclarity.net>
Cc: Rowan Tommins <rowan.collins@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Initializing constants once, with code?
From: robehickman@gmail.com (Robert Hickman)

> > I stand by my comment that this has *some* of the same problems as a
> > separate "build" script, such as the need to be configured correctly,
>
> I find repeating of this as overstating the concern simply because any programming language feature would need to be used correctly.  So this also feels like a distinction without a difference.
>
> > the difficulty of debugging errors in this special code,
>
> Depends? If this where to use XDEBUG just like regular PHP there would be zero difference.
>
> > and the need to invoke the extra processing manually for things like command-line scripts.
>
> Since PHP is different from a pre-compiled language like C or Go, it compiles "on-demand." So I would see zero need for a build step.
>
> I would also see PHP could first run the compile-time code once, and then run the runtime code for every execution. On-demand. And XDEBUG could be used for both.
>
> For CLI, it might always run the runtime code and then the compile time code. Unless there is a standard location set of compiled opcode in .ini file, and/or unless PHP provided ways to generate OpCode artifacts to be loaded at runtime.
>
> -Mike
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

There would be no definite build step in the sense of needing to run a
compiler, as this 'compile time code' would run once during preloading
on web code, and as sugested above, could be ran every time for
command line scripts, but cacheing the opcodes in a file and
automatically detecting changes and recompiling this as python does,
could be a worthwhile optimisation.