Alexey Zakhlestin wrote:
> Enforcing people to use some specific way of coding to use library is
> incorrect, anyway. But, you can correctly handle the situation (i.e.
> provide a meaningful error to the user) by making a simple check:
> http://docs.php.net/headers-sent
With a little bit of magic
On 11/28/07, Ezra Nugroho <[EMAIL PROTECTED]> wrote:
> In my mind, it is still unreliable...
> When I write my library, how can I enforce people who adopt it to enable
> ob?
>
> Furthermore, I think it's quite annoying that some functions may not
> work just because of an inclusion of a blank space
On Nov 28, 2007 12:38 AM, Ezra Nugroho <[EMAIL PROTECTED]> wrote:
>
> On Tue, 2007-11-27 at 14:50 +1000, Rasmus Lerdorf wrote:
> > Ezra Nugroho wrote:
> > > Can I ask for the following support, at least to begin conversation
> > > about it if it hasn't been done before.
> > >
> > > Currently, the h
On Tue, 2007-11-27 at 14:50 +1000, Rasmus Lerdorf wrote:
> Ezra Nugroho wrote:
> > Can I ask for the following support, at least to begin conversation
> > about it if it hasn't been done before.
> >
> > Currently, the header() function still carries the following warning in
> > its online document
Ezra Nugroho wrote:
> Can I ask for the following support, at least to begin conversation
> about it if it hasn't been done before.
>
> Currently, the header() function still carries the following warning in
> its online documentation:
>
> "Remember that header() must be called before any actual
