PureBasic Forums - English

freak wrote:As was announced already previously DX9 support is next on the list, but we
also have many surprises in store for the next version (some already finished),
so wait and see...

I hate suprises

@PB: right

@freak : of course it is one solution for RGB(). But my naive suggestion is for a systematic approach of the compiler applicable to most functions of the PB standard library…

correction: RGB(255,0,0) <-> #FF

Sure?

I try to express a think shared by several people.
Some function call could be removed by their value.

For example:
RGB(255,0,0) is equivalent in #FF0000

Even if RGB() is a function, given x,y,z (means x,y and z are constants) RGB(x,y,z) is a given value too.

So, a possible optimisation could be ...

A little bug using custom keyword syntax highlight:
Given 'a' and 'ab' two custom keywords, now add 'a_a' as a new custom keyword. 'ab' keyword isn’t highlighted anymore...

Small update: the *this\Instance feacture is full operational

Use it to call methods within the methods!

See http://drac.site.chez-alice.fr/Tutorial ... ur_Alerte1

Ok! I see...
Is it revelant to force the compiler to seek the end of a compiler command into macros that follow a starting compiler statement?
In this case, that require a complex macro expansion separating the code above the end statement from the code below the end statement...

I met an other problem with macro + recursiveness but I can't isolate it into a simple example.
I hope is linked to the previous one...

I have some difficulties to handle correctly the set of Include functions in a recursive way:

Given 3 files, there is no bug if the macro called "Ended" is directly substituted by "CompilerEndIf"

file1.pb
XIncludeFile "file3.pb"

XIncludeFile "file2.pb" ; <-- No problem if commented

Start ...

Congratulation to England, Wilkinson and Robinson are performed roles with success, but a small match for French without a Try…
Now, your are the only north hemisphere representative: good luck!

See you tomorrow: a Chabal is unleash

Well, a good match ahead!

Here an improvement of the previous version:
Now, the dynamic array is standalone.
Such an array can be an individual variable or embedded into a structure.
As a consequence, it can be called by referent through a procedure.
;=====================================================
; Array
;
; Dynamic ...

My wish is that IncludePath (or a new command) would be interpreted relative to the owner file.
Without that, all Path need to be absolute and reassigned each time.

Here an example of my current problem:
File1:
IncludePath <Path1>
IncludeFile "File2.pbi"
IncludeFile "File3.pbi"

File2:
IncludePath ...

New update of the OOP set of instructions:

First, a simplification of the class declaration.
The implementation is the same as previous, but the Init_Mbers : EndInit_Mbers block became a private block of the OOP implementation. This private block is used by the new block New : EndNew to perform ...