uld integrate it as easy as
possible if you'd like it.
The answer from Michael Van Canneyt changed my intention, I just want to
develop it
goodbye
ml
>
> ___
> fpc-pascal maillist - fpc-pascal@lists.freepascal.org
> http://lists.fre
a bunch of whining and yapping with my all time favourite "I'm
busy with my day time job" (I think I got that from about 3 of you). Well, I
guess you haven't been busy enough not answer the question I never asked. Never
even considered that instead of yapping about daytime
;
So delphi supports operators? and few other objfpc things?
bwh. but to get serious
Somehow I sound like a bad guy here, that's trying to force his opinion.
Isn't the main reason I try to help here (and I specified it now for at 5 times)
that I don't wanna br
15% (embedded classes)
foreach 0% (well, we know you hate it)
box-type 0% (something like variant, but simpler, better and less memory
consuming)
and some other things which are mostly done, but my best guess is that will be
pascal-off or too-
heretic-like and used by me only.
ml
> _
- use my patch
- send my patch in trash and live without (I won't)
Personaly, I stopped carring (its been a week or two now, and I still haven't
got the answer even where the problem lies)
ml
--
This mail sent throu
laxed or something else mode" is
present, use delphi strict compiler type testing, else use the relaxed types as
they are now in my "in" implementation.
This doesn't mean that patch won't be corrected if I won't like the answer.
Patch (that works just like d
Quoting Florian Klaempfl <[EMAIL PROTECTED]>:
> ml wrote:
>
> > i included again my refcount patch (haven't got even a little response
> > on it. i'm slowly starting to wonder if i'm on the right mailing list
> > (usually devel list is for internal p
only related, then is probably wouldn't make any
sense. "is" is in all other languages is made as safecheck before "as" and
nothing else. No assigning.
ml
--
This mail sent through Horde-Toaster (
at least 4 times asked whom to talk about how to implement). Now
you finally said how. And patch will be corrected to fit constraints.
It is not my project and the last thing I would like would be enforcing unwanted
boundaries (or the lack of it, it can still exist as my patch).
regards
ml
> Mi
Quoting Michael Van Canneyt <[EMAIL PROTECTED]>:
>
>
> On Thu, 31 Mar 2005, ml wrote:
>
> > i included again my refcount patch (haven't got even a little response
> > on it. i'm slowly starting to wonder if i'm on the right mailing list
> &
s)), i got more response on C operators (which i didn't even asked
in fact) than on my first patch and error reports in interfaces)
would include auto_assign_of_guid patch too, but as much as i ask for
somebody involved in compiler nobody answers, that one requires one
change in lower level
On Thu, 2005-03-31 at 02:51 +0200, Michael Van Canneyt wrote:
>
> On Thu, 31 Mar 2005, ml wrote:
>
> It's probably something with the temp variable used in the assignment.
> But the compiler captains would have to confirm that.
>
At first look I suspect it is in tasno
if someone would have idea where
the problem lies. (at least some draft pointer where should I look)
regards
ml
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
RefCount isn't handled correctly if guid <> 0, obviously tests were for
guid 0 only (either when I create guid with md5 or specify in interface
type as {C35224FA-ED88-0D1C-A4D2-FCF91AC4C8C6})
// always using same two variables, and notice all possible calls
// do the same error with counting one
&replace or find
> another term).
>
> [EMAIL PROTECTED] schrieb:
> >>ml schrieb:
> >>Hmmm, Delphi gives a compile time error if "as" is used on an interface
> >> [...]
> >>
> > This is doable, patch can contain both with compiler direc
Quoting Thomas Schatzl <[EMAIL PROTECTED]>:
> Hello,
>
> ml schrieb:
> Hmmm, Delphi gives a compile time error if "as" is used on an interface
> without GUID, same for support()... since both use the interfaces IID to
> query for existence of an
I made one wrong statement.
It's not "as" that doesn't work. getinterfaceentry works only for
interfaces that have guid specified. By default guid is zeroed, and
getinterfaceentry just returns first interface in table, which means
wrong. Same problem shows in Support too.
writing guid like ['{000
.5 (and have yet to set one windows box to
test on). Will this do?
>
> As for querying the class behind the interface: first you need to answer the
> windows problem.
>
As soon as I finish my patch for "as" and "is" I'll implement it so that
it will handl
On Thu, 2005-03-24 at 15:01 +0100, Michael Van Canneyt wrote:
>
> On Thu, 24 Mar 2005, ml wrote:
>
> > On Thu, 2005-03-24 at 09:06 +0100, Michael Van Canneyt wrote:
> >>
> >> On Thu, 24 Mar 2005 [EMAIL PROTECTED] wrote:
> >>
> >
> ...
> end;
>
> function TFactory.newPublic: IPublic;
> begin
>
> Result := TPrivate.Create; // or implement some kind of class
>// pooling etc ..
> end;
>
gt; >>
> >>> Quoting Marco van de Voort <[EMAIL PROTECTED]>:
> >>>
> >>>>> On Tue, 22 Mar 2005, ml wrote:
> >>>>>> // than one interface
> >>>>>> a := (object as IA); // correct
> >>>&
Quoting Michael Van Canneyt <[EMAIL PROTECTED]>:
>
>
> On Wed, 23 Mar 2005 [EMAIL PROTECTED] wrote:
>
> > Quoting Marco van de Voort <[EMAIL PROTECTED]>:
> >
> >>> On Tue, 22 Mar 2005, ml wrote:
> >>>> // than one interface
>
Quoting Marco van de Voort <[EMAIL PROTECTED]>:
> > On Tue, 22 Mar 2005, ml wrote:
> > > // than one interface
> > > a := (object as IA); // correct
> > > b := (object as IB); // returns pointer to the first interface
vmt=IA
> > > c := (object a
> > Quoting Marco van de Voort <[EMAIL PROTECTED]>:
Like first, I wouldn't like to spam this mailing list about interfaces.
Can I contact you directly or somewhere else?
I would like to try to patch some things but I would probably have few
questions how to implement it to satisfy everybody, or
Quoting Marco van de Voort <[EMAIL PROTECTED]>:
>
> Afaik not, you have a pointer to an interface table, And even if you can get
> to the object vmt from there, you don't know anything about it. interface is
> all about information hiding. It might not even be a proper Pascal object.
>
> No, the
inherit ICountable in IAccessible, IAccessible in IRemovable.
Which would lead that instead of having simple IModifiable, IModifiable would
contain bunch of declarations which mostly wouldn't be needed. While in multiple
inheritance
having separate IModifiable is possible. And r
On Sun, 2005-03-20 at 02:55 +0200, Nikolay Nikolov wrote:
> ml wrote:
>
> >Other possibilities like ['?','%','$','|','&','::','^'] were only named
> >under btw. (and how can btw. under question
add things like this to the language, I think that
> the free pascal compiler's source code is all included, written (mostly)
> in pascal itself, and I've heard that it's self-compilable, so you already
> have all the tools to develop your own extended pascal language.
>
Alre
On Sat, 2005-03-19 at 03:55 +0200, Nikolay Nikolov wrote:
> ml wrote:
>
> >3. This one is not some little beauty hack. So, no pressure here. But, I
> >must admit that I'm most interested in this answer. Classes do support
> >multiple interface inheritance, but inter
On Sat, 2005-03-19 at 01:40 +0200, Nikolay Nikolov wrote:
> ml wrote:
>
> >btw. When writing about operators, why do they contain such little
> >possibilities. operator overloads could contain possibility for
> >['?','%','$','|',
face inheritance, but interfaces don't. That cuts almost
all of the interface flexibility. Any good reasons why?
Sincerely
ml
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
31 matches
Mail list logo
