Re: [INTERNALS-WIN] [PATCH] Static dependency errors

[email protected] ("Steph Fox")
Newsgroups php.internals.win
Message-ID <000b01c8e9df$f79e61b0$a7bd614d@foxbox>
Hi Pierre,

> As part of online discussion and IRC, we already define this behavior.
> It was also discussion to have different levels of configure errors
> (warning, fatal, etc.). The idea is also to display only the relevant
> information and it is what the summary begin to do (while leaving the
> possibility to have a verbose and noisy output as now).

Not being party to this discussion, I'm not entirely sure what you mean 
here.

> You may consider to discuss things off list.  You would have been told
> to wait a couple of days instead (Rob knows it but he may have forgot
> to mention that in your discussions) as I already said that I'm
> working on these changes.

That's precisely why a patch and not a commit, although I have to say Rob 
didn't specifically say that other work being done in this area.

> The changes I made (like for DOM) are part of this task and are
> desired, they will remain like it is now.

I think that's very much open to discussion. Who desires messed-up local 
configuration files, and why?

As a (small) proof of its
> goodness, you can now build php without having any library available
> but resolv.lib (and this one will be dropped soon as well).

You can do that with my patch, too.

> About the difficulty to write config.32, I can't agree. It is very
> easy to write a config.w32 file for Windows, even with our recent
> changes (which are only about checking that a given requirement is
> full filled).

Those changes in local configuration files actually cause dependency logic 
to be avoided.

> The unix-like output is the worst thing ever, it is almost impossible
> to quickly match the relevant warning or errors.  Many newbies even
> prefer the new outputs instead of the unreadable unix-like one. They
> ask for more improvements like that.

Where are all these people and where are all those requests?

> I'm sorry but I'm not in favor of applying this patch as it covers
> something that is covered by the upcoming error level and logging
> option. Please don't commit it.

Could you point me to some discussion of this upcoming error level and 
logging option?

Thanks,

- Steph

>
>
> Cheers,
> ---
> Pierre
>
> http://blog.thepimp.net | http://www.libgd.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.