I have been following the thread and having come from VS and VB, I dont
get the point of Making RB from RB.
1- Wouldnt C++ give you everything you need to create a massive
developing tool?
2- Shouldnt RB test their stuff before releasing it? If they tested or
debug the application and features they are releasing, shouldnt all this
bugs be fixed?
3- Are we paying beta testers?
It seems to me that the issues should not be DEVELOP USING RB, it should
be, why was this feature untested and who is responsible for those
features and their releases.
I mean, after sitting here reading the threads, I have noticed that some
of you are top notch programmers, why isnt RS paying attention or are they?
I fail to see why they have to develop in RB, if RB is bugged as it it,
it also means that the products being produced by RB are also bugged?
Daniel Stenning wrote:
Inlining would be a useful thing in itself, but I would still hate having
to type in those inline wrappers
On 1/2/07 18:59, "Frank Condello" <[EMAIL PROTECTED]> wrote:
On 1-Feb-07, at 12:40 PM, Norman Palardy wrote:
On Feb 01, 2007, at 10:05 AM, Daniel Stenning wrote:
Namespaces would indeed be very helpful - for two reasons:
1) it would allow for a better way of accessing Declares. A
whole bunch of
declares could be put inside a given namespace,m removing the need
to have
to keep declaring the same API functions inside every RB method
that calls
it
2) it would facilitate much better support for incorporating 3rd
party code
into projects - whether RB based through DLL declares or plugins.
My idea for namespaces would be to implement them simply as a
special type
of RB project folder. Any RB class, module,interface or window
placed
inside such a folder would then be accessed by using the namespace
name as a
dot prefix.
A module with methods works for this
Create a method that wraps the declare once and use the heck out of it
That is rb's namespace mechanism at the moment
If RB could inline these wrapper methods that might actually be
useful!
Inlining would be a useful thing in itself, but I would still hate having
to type in those inline wrappers
I don't really get the namespace request but a way to define
a declare once and use it everywhere (or define it once in a class
and use it there) would be hugely helpful.
I agree - namespaces arent necessarily the best way of making declares
easier to use globally, I was kind of implicitly suggesting en extra feature
there - but I do think that tying declares to namespaces is useful because
declares tend to be from 3rd pty libraries OS or otherwise, and there are
often naming conflicts that can arise.
I recall a time when you
could drag a library into the project and defining entry points -
decalres seem a bit backwards in comparison...
Sounds like a good thing to me, was this in an older version of RB >
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
