What is so exciting of " ()" and " ==" ?
fruit = Banana()
fruit = Banana
fruit = Banana ...
if fruit = Banana then ...
function Banana( dword a, dword b)
... do some things with a and b
... and then do:
result a == b
end function
otherwise your brain could fall outthis happens often. :D
There is a reason for not enforcing brackets and perhaps blurring the distinction between variables and procedures.
There is Nokia's QT which is quite interesting as it compiles to Native Windows, Linux and Mac. Oxygen written in QT would be interesting as it has a great framework from which to launch from and QT does not have a BASIC version, so that is a good fit.
... and a new compiler called clang. 2 to 3 times faster in compiling than gcc and captures many errors that other compilers miss. In fact, many major projects are advertising passed through clang. For example, in one of the videos I watched, they said code that came out squeaky clean no errors in gcc, had around 150 errors in clang identified. clang is now becoming the Mac compiler of choice. clang is also connected to LLVM in ways I don't understand at the moment.
because Win32 is dying.do not fall into panic now. :D
Then... efgee Oxygen basic is not for you.
Windows dying ...yes because MacOS & Linux use only cca 5% people on planet :P
do you know where you living...
efgee
In your observation there are to many contra-points and sounds like i don't
know about what i talk...man...
maybe you think that i'm stupid or something... >:(
your feelings are not my theritory
and from your post i see that you don't know many things
Metro style is HTML5 style of programming if you don't know that... ::)
And you say win32 api is not of my interest ...man ...gee
do you know where you living... ???
A C emitter is certainly the next milestone for Oxygen, but in terms of library development it's more of an organic process.
I am not overly concerned about repetition. If a repeating code pattern becomes evident, it will be assimilated into a library at some point.
I think Win32 will always be present, even if most programs do not use it directly - much of Win32 forms the base of the pyramid.
Charles
At least on the bright side, Microsoft will support Windows 7 until 2020.
What is the GUI model in OSX, Frank? Does it use anything like the MS messaging system, with message loop and Wndproc callbacks?
Charles
int main(int argc, char *argv[]) {
NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
[NSApplication sharedApplication];
int style = NSClosableWindowMask | NSResizableWindowMask | NSTexturedBackgroundWindowMask |
NSTitledWindowMask | NSMiniaturizableWindowMask;
NSWindow *win = [[NSWindow alloc] initWithContentRect:NSMakeRect(50, 50, 600, 400)
styleMask:style
backing:NSBackingStoreBuffered
defer:NO];
[win makeKeyAndOrderFront:win];
[NSApp run];
[pool release];
}
It is of course, all too easy to create evil mind-destroying code with macros
However if Oxygen really goes to only C++ OOP direction i will give up.
I am not evil enough tonight to dream up a really bad macro, Aurel. Smiley
You can use a macro as an alternative to a callback function.
macro keyboard()
case wm_keydown
...
case wm_char
...
end macro
This can be used to expose part of wndproc to the user, up-front. A large WndProc can thus be split into manageable sections: keyboard, mouse, timed-events, resize etc.
Charles