Hi Marcus,
I think that the idea of ini preprocessing is great, however I would
like little bit different syntax.
a) I think we don't need (1) ternary support at all, as (2)
if-elif=else-endif may do the same.
b) I think usage of square brackets is not a good idea, because they are
commonl
On Fri, 2008-02-15 at 11:36 +0300, Dmitry Stogov wrote:
> a) I think we don't need (1) ternary support at all, as (2)
> if-elif=else-endif may do the same.
That was already dropped. :)
> b) I think usage of square brackets is not a good idea, because they are
> commonly used to divide ini files
Jani Taskinen wrote:
On Fri, 2008-02-15 at 11:36 +0300, Dmitry Stogov wrote:
a) I think we don't need (1) ternary support at all, as (2)
if-elif=else-endif may do the same.
That was already dropped. :)
b) I think usage of square brackets is not a good idea, because they are
commonly used t
the semantic of "NOWDOC with double quotes" should be the same as HEREDOC.
Dmitry.
Lars Strojny wrote:
Hi,
I know, I might be a bit late but I've played around with NOWDOCS and
one issue popped up instantly: it seems not really logical to me, why
only single quotes are allowed and I have the f
On Fri, 2008-02-15 at 13:02 +0300, Dmitry Stogov wrote:
> Jani Taskinen wrote:
> >> c) We can use just "value" insted of ${value} in conditions.
> >
> > Yup. ${foobar} is actually not any "variable" per se, but just a
> > reference to existing ini entry in the file. And I don't think that
> > need
#if defined(PHP_MAJOR_VERSION) && PHP_MAJOR_VERSION >= 6
extension="unicode.so"
#endif
Here PHP_MAJOR_VERSION is a PHP constant that is not defined in php-5.3
but might be defined in the future version.
Dmitry.
Jani Taskinen wrote:
On Fri, 2008-02-15 at 13:02 +0300, Dmitry Stogov wrote:
Ja
Hello Dmitry,
shouldn't this be like in C/C++ where a non existing value is treated like
an empty string which behaves like false in boolean evaluations?
marcus
Friday, February 15, 2008, 11:25:42 AM, you wrote:
> #if defined(PHP_MAJOR_VERSION) && PHP_MAJOR_VERSION >= 6
> extension="unicode.s
Hello Jani,
Friday, February 15, 2008, 10:30:15 AM, you wrote:
>> b) I think usage of square brackets is not a good idea, because they are
>> commonly used to divide ini files into sections. Why not to use C
>> syntax? (#if...)
> I'd prefer that syntax too, it would be much clearer than mixing
I think it will work.
#ifdef UNDEFINED > 5 (false)
#ifdef UNDEFINED <= 5 (true)
(but anyway I think it is possible to find out an unclear condition)
Dmitry.
Marcus Boerger wrote:
Hello Dmitry,
shouldn't this be like in C/C++ where a non existing value is treated like
an empty string which
Marcus Boerger kirjoitti:
Hello Jani,
Friday, February 15, 2008, 10:30:15 AM, you wrote:
b) I think usage of square brackets is not a good idea, because they are
commonly used to divide ini files into sections. Why not to use C
syntax? (#if...)
I'd prefer that syntax too, it would be much
When I think INI I think constants. What happens when I log into some
server I have to debug some app instance and one of the first things I
might do is check the INI and I see.
[IF ${value} == 1]
setting = 1
[ELIF ${value} == 2]
[IF ${valuex} == 1]
setting = 1
[ELIF ${valuex} == 2]
setting
Currently UNDEFINED would be just string 'UNDEFINED'.
Doesn't atoi() for non-numeric string make it 0 ??
(or null..:) So that would work without changing anything..
--Jani
Dmitry Stogov kirjoitti:
I think it will work.
#ifdef UNDEFINED > 5 (false)
#ifdef UNDEFINED <= 5 (true)
(but anyway I
Chris Stockton wrote:
When I think INI I think constants. What happens when I log into some
server I have to debug some app instance and one of the first things I
might do is check the INI and I see.
[IF ${value} == 1]
setting = 1
[ELIF ${value} == 2]
[IF ${valuex} == 1]
setting = 1
[ELIF ${
Now that what-if's are occurring in the theoretical world of
intelligent INI, what about file testing capabilities so that the
following can be used to preload extensions by existance?
#if -f ${EXTENSIONS_DIR}/gd.so
extension=gd.so
#endif
or some other syntax that allows testing to include a
Dmitry, please don't throw gasoline on the flames.
We have to keep the ini files as simple as possible, this isn't the job of
the ini file.
--Jani
Dmitry Stogov kirjoitti:
The idea makes sense too, but mix of C and SH syntax isn't good.
Dmitry.
BuildSmart wrote:
Now that what-if's are occurr
Hi,
A few days ago I posted the same problem to the php-general list and I
had no luck with an answer. Maybe someone on this list has some
knowledge with ldap authentication?
I try to authenticate users with LDAP at an Active Directory Server
(AD). Everything works fine. Just in some cases, authe
Hi Marcus,
On Wed, Feb 13, 2008 at 5:26 PM, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> Also I reduced the number of added values to 'php.zts' and 'php.debug'.
> Maybe we can add those two as consts (Pierre?).
Done, both PHP_DEBUG (same as ZEND_DEBUG) and PHP_ZTS, in 5.3 and HEAD.
--
Pierre
h
Hi,
Am Freitag, den 15.02.2008, 13:07 +0300 schrieb Dmitry Stogov:
> the semantic of "NOWDOC with double quotes" should be the same as HEREDOC.
Puh, I'm not really sure about that. I guess this will be even more
confusing.
cu, Lars
signature.asc
Description: Dies ist ein digital signierter Nac
The if-else is very basic thing. And it's quite necessary to make the
"user.ini" stuff useful. Especially for hosting companies.
If someone abuses it, they're pretty much on their own anyway.
--Jani
Chris Stockton kirjoitti:
It might be to late to keep it simple, once you add basic language
c
Oh ya, that is why PHP isn't widely adopted in the shared hosting
world. Oh btw, I really do think we should give our users bigger guns
to shoot themselves in the foot with. We already know that if we give
them features that could be used incorrectly, they won't use them
incorrectly.
This mess
It might be to late to keep it simple, once you add basic language
components like IF-ELSE as you can see people already want basically
another programming language embedded into it. It is my opinion that
the INI files should be simple configuration files. Otherwise they
will become more and more f
The idea makes sense too, but mix of C and SH syntax isn't good.
Dmitry.
BuildSmart wrote:
Now that what-if's are occurring in the theoretical world of intelligent
INI, what about file testing capabilities so that the following can be
used to preload extensions by existance?
#if -f ${EXTENSI
I know I am a bit late, but I've played around with NOWDOCS this
evening, and one issue thing came up instantly: I asked myself why the
heck are single quotes allowed but not double quotes? This seems to me
You mean around end token? Because there's no need in them. We already
have double quote
Take a look at apache's config mechanism, it allows conditional
arguments.
Yes, it can be abused but we're not talking about an extensive INI
language, just something covering basic conditional control.
On Feb 15, 2008, at 9:48 AM, Chris Stockton wrote:
It might be to late to keep it simp
http://en.wikipedia.org/wiki/Here_document
See the Perl's HEREDOC definition.
Dmitry.
Lars Strojny wrote:
Hi,
Am Freitag, den 15.02.2008, 13:07 +0300 schrieb Dmitry Stogov:
the semantic of "NOWDOC with double quotes" should be the same as HEREDOC.
Puh, I'm not really sure about that. I gue
Hello Pierre,
cool & thx
marcus
Friday, February 15, 2008, 4:10:54 PM, you wrote:
> Hi Marcus,
> On Wed, Feb 13, 2008 at 5:26 PM, Marcus Boerger <[EMAIL PROTECTED]> wrote:
>> Also I reduced the number of added values to 'php.zts' and 'php.debug'.
>> Maybe we can add those two as consts (Pi
On Feb 13, 2008, at 1:50 PM, Stanislav Malyshev wrote:
Yes, that's why php.ini-recommended should have GP. However,
php.ini-dist documents *the default* - which should be GPC, like
it is right now.
The default is NULL, which means using variables_order - just as
before. I don't see a lo
I'm with Dmitry - but syntax aside, the only way this becomes even halfway
important is if the whole PECL scenario is sorted out in a way that makes
good sense to the end users.
Back to square one. Sorry guys but sooner or later this has to be dealt
with. We need to be sure of what a PHP insta
Hi all,
I've heard that E_DEPRECATED is still missing nevertheless its
introduction is planned for 5.3. So I've wrote it [1] based on a
slightly outdated patch by Felipe. The patch is so far complete, as far
as I can tell, but one thing I'm wondering about is whether we should
trigger E_DEPRECATED
29 matches
Mail list logo
