Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #4511
| From | Carlos Rocha <carlos.rocha@doossier.com.removethis> |
|---|---|
| Newsgroups | comp.lang.clipper.visual-objects |
| Subject | Re: About VO 2.8 SP4 |
| Date | 2012-12-22 19:31 +0000 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <kb51sa$q68$1@speranza.aioe.org> (permalink) |
| References | <143c7a9e-df41-48ef-b63a-758ebbb59f46@googlegroups.com> |
First impressions:
>
> 1. Support for ByteArrays. With SP3 we have the option to receive them as Strings, but it's not possible to send them back as ByteArrays.
> 2. Support for Variants passed by reference in events. Actually they are received as Usuals and therefore unusable.
No. Maybe someday some user "asks" for it :/
>
> Of course other matters interest me too, like stability, Debug...
Seems better overall, but I still get the "Sorry..." button if I use the
debug.
With the new pair OLE runtime/OleAutoObjectEx I found an old obscure bug
in my code:
When some Access/Method that returns another OleAutoObject doesn't
return the "real" object I usually cast it like
local oRealObject as TheRealObject
oRealObject := TheRealObject{MyGeneratedClass:SomeAccess}
oRealObject:Color := Rgb(R,G,B)
This way I can use the specific properties of TheRealObject that might
not exist in the original (generated) uRetVale, and is also useful to
call declared methods for early binding.
I was casting an object to a wrong one by mistake (since VO 2.7 ?), but
with SP4 the runtime detected it (with an exception, of course).
> Finally...what new bugs were introduced in SP4, if any?
>
The "Automation Server..." generated repeated code for different objects
in a few occasions. It's easy to detect, and deleting and generating
again solves it. Never happened to me with previous versions.
The compiler is really much faster, but sometimes one need to touch some
modules/applications by hand or the binary (.DBG) isn't updated accordingly.
I tried to correct the introduced bug in RGB() - now returns a Dword,
like nobody else :/
_dll FUNCTION RgbAsDWord(bR, bG, bB as byte) as DWORD PASCAL:VO28RUN.Rgb
function RGB(bR, bG, bB as byte) as long pascal
return long(_cast, RgbAsDWord(bR, bG, bB))
but I get a runtime message stating that "the entry point to RGB was not
found in VO28RUN" if running from the IDE, but the EXE runs fine.
In conclusion, overall SP4 is better than SP3 and my program apparently
runs faster and is smaller (gotta check why - 18.9 MB to 15.6 MB seems
too much).
--
Carlos Rocha
Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
About VO 2.8 SP4 Carlos Rocha <jazzda1307@gmail.com> - 2012-12-18 18:14 -0800
Re: About VO 2.8 SP4 Carlos Rocha <jazzda1307@gmail.com> - 2012-12-19 10:16 -0800
Re: About VO 2.8 SP4 James Martin <jmmicmc@cyg.net> - 2012-12-19 11:05 -0800
Re: About VO 2.8 SP4 Carlos Rocha <carlos.rocha@doossier.com.removethis> - 2012-12-22 19:31 +0000
Re: About VO 2.8 SP4 Carlos Rocha <carlos.rocha@doossier.com.removethis> - 2012-12-22 22:35 +0000
Re: About VO 2.8 SP4 Carlos Rocha <jazzda1307@gmail.com> - 2012-12-22 17:42 -0800
Re: About VO 2.8 SP4 igsofterror@gmail.com - 2012-12-23 13:57 -0800
Re: About VO 2.8 SP4 Carlos Rocha <carlos.rocha@doossier.com.removethis> - 2012-12-23 23:34 +0000
csiph-web