In our previous episode, Jonas Maebe said:
> > On 1 July 2010 10:04, Michael Van Canneyt wrote:
> >>
> >> And as I understood it, Marco explicitly mentioned that it is not merged
> >> back to fixes. It also does not appear in
> >> http://www.stack.nl/~marcov/fpctomerge.txt
> >
> > You do you mean,
Graeme Geldenhuys wrote on Thu, 01 Jul 2010:
On 1 July 2010 10:04, Michael Van Canneyt wrote:
And as I understood it, Marco explicitly mentioned that it is not merged
back to fixes. It also does not appear in
http://www.stack.nl/~marcov/fpctomerge.txt
You do you mean, I clearly see it liste
On Thu, 1 Jul 2010, ik wrote:
On Thu, Jul 1, 2010 at 10:54, Michael Van Canneyt wrote:
On Thu, 1 Jul 2010, ik wrote:
On Thu, Jul 1, 2010 at 10:33, Michael Van Canneyt
wrote:
In all fairness, deprecated normally means it is "marked" as deprecated
at
least for one release *before* it
In our previous episode, Graeme Geldenhuys said:
>
> Maybe adding it as a {$warning This unit is deprecated} will suffice
> for now, until r14767 is merged with 2.4.x. I just tested {$warning
> ...} below the 'unit ...;' line, and indeed it does output a warning
> in the compiler output.
I alread
On 1 July 2010 10:06, Marco van de Voort wrote:
>> code in 2.4.x should FIRST be marked as deprecated for one release (maybe
>> even as soon as FPC 2.4.2 seeing that the 'deprecated' hint directive
>> doesn't break anything).
>
> We all know that, but we don't do that for a reason:
>
> Unit level d
On 1 July 2010 10:04, Michael Van Canneyt wrote:
>
> And as I understood it, Marco explicitly mentioned that it is not merged
> back to fixes. It also does not appear in
> http://www.stack.nl/~marcov/fpctomerge.txt
You do you mean, I clearly see it listed in fpctomerge.txt (I just
double checked)
On Thu, Jul 1, 2010 at 10:54, Michael Van Canneyt wrote:
>
>
> On Thu, 1 Jul 2010, ik wrote:
>
> On Thu, Jul 1, 2010 at 10:33, Michael Van Canneyt > >wrote:
>>
>> In all fairness, deprecated normally means it is "marked" as deprecated
at
least for one release *before* it gets deleted.
In our previous episode, Graeme Geldenhuys said:
> > Fixes still contains it. Most of the fpweb changes are not merged back to
> > 2.4.x
>
> As usual you don't understand me correctly, as your above statement proves.
> Let me explain again. The r15346 should not be merged to 2.4.x yet,
(or at all
On Thu, 1 Jul 2010, Graeme Geldenhuys wrote:
Op 2010-07-01 09:33, Michael Van Canneyt het geskryf:
And since the code was not being maintained anyway, he could just have kept the
latest copy of it: so no harm done.
Either way, see my reply to Marco. Your actions might have been ok for
Trun
On Thu, 1 Jul 2010, ik wrote:
On Thu, Jul 1, 2010 at 10:33, Michael Van Canneyt wrote:
In all fairness, deprecated normally means it is "marked" as deprecated at
least for one release *before* it gets deleted. If I was ik, I'd be
pretty
pissed off working on a project that might be released
Op 2010-07-01 09:44, ik het geskryf:
> existed code that works on other servers), and I prefer to use something
> stable and fast rather then something that is not, because I do not have
> a lot of time to make things work properly (the life of freelancing).
This is exactly the point I was trying
Op 2010-07-01 09:33, Michael Van Canneyt het geskryf:
>
> And since the code was not being maintained anyway, he could just have kept
> the
> latest copy of it: so no harm done.
Either way, see my reply to Marco. Your actions might have been ok for
Trunk, but definitely will not be for the stabl
On Thu, Jul 1, 2010 at 10:33, Michael Van Canneyt wrote:
>
>
> On Thu, 1 Jul 2010, Graeme Geldenhuys wrote:
>
> Op 2010-06-30 18:00, Jonas Maebe het geskryf:
>>
>>>
>>> * Deprecated in favour of fcl-web and WST
>>>
>>
>> In all fairness, deprecated normally means it is "marked" as deprecated at
>
Op 2010-07-01 09:15, Marco van de Voort het geskryf:
>
> Fixes still contains it. Most of the fpweb changes are not merged back to
> 2.4.x
As usual you don't understand me correctly, as your above statement proves.
Let me explain again. The r15346 should not be merged to 2.4.x yet, the
code in 2.
On Thu, 1 Jul 2010, Graeme Geldenhuys wrote:
Op 2010-06-30 18:00, Jonas Maebe het geskryf:
* Deprecated in favour of fcl-web and WST
In all fairness, deprecated normally means it is "marked" as deprecated at
least for one release *before* it gets deleted. If I was ik, I'd be pretty
pissed
In our previous episode, Graeme Geldenhuys said:
> > * Deprecated in favour of fcl-web and WST
>
> In all fairness, deprecated normally means it is "marked" as deprecated at
> least for one release *before* it gets deleted. If I was ik, I'd be pretty
> pissed off working on a project that might b
Op 2010-06-30 18:00, Jonas Maebe het geskryf:
>
> * Deprecated in favour of fcl-web and WST
In all fairness, deprecated normally means it is "marked" as deprecated at
least for one release *before* it gets deleted. If I was ik, I'd be pretty
pissed off working on a project that might be released
On Wed, 30 Jun 2010, ik wrote:
Thanks,
I do not understand how do I create an xmlrpc server using fcl-web
0. Start an fcl-web application.
1. Create an interface and an implementation using WST.
(WST has plenty of examples. Easiest is to define an interface
MyInterface = Interface [
Thanks,
I do not understand how do I create an xmlrpc server using fcl-web
Ido
On Wed, Jun 30, 2010 at 19:00, Jonas Maebe wrote:
>
> On 30 Jun 2010, at 17:37, ik wrote:
>
> > It seems that the xmlrpc unit is missing from fpc source tree (trunk).
> > Was it renamed (to what) or was it remove
On 30 Jun 2010, at 17:37, ik wrote:
> It seems that the xmlrpc unit is missing from fpc source tree (trunk).
> Was it renamed (to what) or was it remove (why was that) ?
r15346 | michael | 2010-05-30 16:14:18 +0200 (Sun, 30 May 2010) | 1 line
Changed paths:
D /trunk/packages/fcl-net/src/httpb
Hello List,
It seems that the xmlrpc unit is missing from fpc source tree (trunk).
Was it renamed (to what) or was it remove (why was that) ?
Thanks,
Ido
http://ik.homelinux.org/
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.
21 matches
Mail list logo