🚀 go-pugleaf

Here are the lines:

2526:   function IndyLength(const ABuffer: String; const ALength: Integer 
= -1; const AIndex: Integer = 1): Integer;
2527:   begin
2528:     Assert(AIndex >= 1);
2529:     if ALength < 0 then begin
2530:       Result := Length(ABuffer)-AIndex+1;
2531:     end else begin
2532:       Result := Min(Length(ABuffer)-AIndex+1, ALength);
2533:     end;
2534:   end;


Thanks again,


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4679fa58$1@newsgroups.borland.com...
>
> "JLoz" <jfsierra@excite.com> wrote in message
> news:4679c15b$2@newsgroups.borland.com...
>
>> The error message I get is
>>
>> EAssertion Failed with 'Assertion Failure IdGloba.pas Line 2528'
>
> It would be helpful if you would show what is actually on that line.
> There have been so many releases and snapshots of Indy, there is no
> way to know which one you are actually using.  For instance, there is
> no assertion on that line in my copy of IdGlobal.pas.  Line 2528 is
> inside the TIdLocalEvent constructor.
>
>> The way the attachments are sent is different from what I was
>> accostumed to do with Indy 9
>
> Attachments work the same as they did in Indy 9.  The only difference
> is that Indy 9 supported only file attachments whereas Indy 10
> supports a customizable attachment model.  So the TIdAttachment class
> is now an abstract base class in Indy 10 and can't be instantiated
> directly anymore.  TIdAttachmentFile in Indy 10 is the direct
> replacement for TIdAttachment in Indy 9.  Most of your code that used
> TIdAttachment in Indy 9 does not need to change in Indy 10, as the
> methods/properties are the same.  The only real change you need to
> when you instantiate a new attachment, which you already updated that
> code.
>
>> I had problems trying to use IdAttachementFile as it was not being
> recognized.
>
> Then you did not read the documentation, as it tells you which unit
> each class/component is declared in.
>
>
> Gambit
>
>