On Sat, 4 Nov 2006, Ales Katona wrote:
> Wanted to ask, how should I process the URL?
>
> Should I also understand ":" as separator for port eg:
> http://www.shit.com:3030 ?
>
> Shouldn't this be parsed by some common function? Eg:
> procedure ParseURL(var Host, URI: string; var Port: string);
Wanted to ask, how should I process the URL?
Should I also understand ":" as separator for port eg:
http://www.shit.com:3030 ?
Shouldn't this be parsed by some common function? Eg:
procedure ParseURL(var Host, URI: string; var Port: string);
This way we can save the hassle for all the backends a
Oh DOH thanks, it was the pointer stuff. Sometimes I wished fpc warned
if you pass a pointer to untyped var.
In any case pkglnet.pas is in now, I tested with the example and it
worked. Only HTTP yet, but I'll do FTP ASAP.
Ales
___
fpc-devel maillist -
> Ok I tested it and I got an odd bug.
>
> When I "writeln" the buffer contents before writing them to the Dest
> stream, they are ok. But the resulting file is a garbage of xterm crap
> (mostly symbols) with exactly same size as the thing I downloaded
> (completly different data).
>
> I've no id
Ok I tested it and I got an odd bug.
When I "writeln" the buffer contents before writing them to the Dest
stream, they are ok. But the resulting file is a garbage of xterm crap
(mostly symbols) with exactly same size as the thing I downloaded
(completly different data).
I've no idea where to look
On Sat, 4 Nov 2006, Ales Katona wrote:
> > - lnet (Ales, will you do this or not, I was actually waiting with my
> > implementation?)
>
> I mailed you yesterday, I get this error trying to compile fppkg:
>
> Target OS: FreeBSD/ELF for i386
> Compiling fprepos.pp
> Fatal: Can't find unit strea
On so , 2006-11-04 at 18:17 +0100, Marco van de Voort wrote:
> streamcoll
>
> My "make all install" on freebsd of this morning installed a unit
> streamcoll, so probably already fixed.
I confirm, latest 2.1.1 works.
___
fpc-devel maillist - fpc-devel
> > - lnet (Ales, will you do this or not, I was actually waiting with my
> > implementation?)
>
> I mailed you yesterday, I get this error trying to compile fppkg:
>
> Target OS: FreeBSD/ELF for i386
> Compiling fprepos.pp
> Fatal: Can't find unit streamcoll
My "make all install" on freebsd of
> - lnet (Ales, will you do this or not, I was actually waiting with my
> implementation?)
I mailed you yesterday, I get this error trying to compile fppkg:
Target OS: FreeBSD/ELF for i386
Compiling fprepos.pp
Fatal: Can't find unit streamcoll
Seems it's either not installed with fcl or there's
On Sat, 4 Nov 2006, Marco van de Voort wrote:
> > On Fri, 3 Nov 2006, Ales Katona wrote:
> > > I'm willing to add the required networking support to the packager if
> > > you guys tell me "how". I mean, should I add lNet as a choice to
> > > package/base or fcl (not sure on which the packager ac
Marco van de Voort wrote:
Synapse too? Why not Indy then? :-)
yes, indy run on arm-wince :-)
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
> On Fri, 3 Nov 2006, Ales Katona wrote:
> > I'm willing to add the required networking support to the packager if
> > you guys tell me "how". I mean, should I add lNet as a choice to
> > package/base or fcl (not sure on which the packager actualy depends), or
> > just "inside" the packager (eg: no
On Fri, 3 Nov 2006, Ales Katona wrote:
>
> > I am already adding lnet and synapse support to fppkg.
> > (to WST too, BTW ;) ) The wget is a fallback and proof
> > of concept implementation.
>
> I've got a skeleton lNet/fppkg done localy now, will finish it tomorrow
> (and hopefuly find a wa
> I am already adding lnet and synapse support to fppkg.
> (to WST too, BTW ;) ) The wget is a fallback and proof
> of concept implementation.
I've got a skeleton lNet/fppkg done localy now, will finish it tomorrow
(and hopefuly find a way to test :) )
I've put lNet to fcl for local setup too
On Fri, 3 Nov 2006, Ales Katona wrote:
> I've noticed Michael just added a "wget" package getter to the new
> packager.
Yes.
>
> We already had a small discussion about using lNet in the new packaging
> system and it comes down to this:
>
> The packager needs pure fpc solution, which lNet no
15 matches
Mail list logo
