Folks,
I've added the VSIFReadL function and updated the VSIFWriteL function in
the Perl bindings. I added simple tests for those and for VSIFOpenL and
VSIFCLoseL functions to the Perl binding tests.
I added VSIFReadL and VSIFWriteL function prototypes to cpl.i as they
are in the GDAL source
On 11/20/2011 01:34 PM, Even Rouault wrote:
But it turns out that while this works, it is not optimal, since in a
WFS case there may be
errors during the production of the GML and it should be buffered before
sending to
the client - otherwise the error message XML gets mixed up with the GML.
I'm
> For CGI "/dev/stdout" works with trunk but it does not work with
> released versions.
> I was confused (I was using two different computers with two different
> setups) and
> as a result my mails were confused, sorry.
>
> After some more careful testing my final conclusion is the above. The
> on
On 11/20/2011 12:50 PM, Even Rouault wrote:
Le dimanche 20 novembre 2011 10:04:50, Ari Jolma a écrit :
On 11/19/2011 04:24 PM, Even Rouault wrote:
I found the problem. It is changeset 23022 (by you, Even :), which
removes support for "stdout" and adds "/dev/stdout" as an alias to
"/vsistdout/".
Le dimanche 20 novembre 2011 10:04:50, Ari Jolma a écrit :
> On 11/19/2011 04:24 PM, Even Rouault wrote:
> >> I found the problem. It is changeset 23022 (by you, Even :), which
> >> removes support for "stdout" and adds "/dev/stdout" as an alias to
> >> "/vsistdout/". Simple, but took me a while to
On 11/19/2011 04:24 PM, Even Rouault wrote:
I found the problem. It is changeset 23022 (by you, Even :), which
removes support for "stdout" and adds "/dev/stdout" as an alias to
"/vsistdout/". Simple, but took me a while to find out especially as the
log message begins "mentions in the doc".
Hum
