The FB manual on: ReDim clearly states -- declaring a dynamic array.
Therefore, the 'mystery' claim, seems to be 'unfounded'!
Search found 2770 matches
Sorry, you proposed to use 32-bit code inside 64-bit code Equally sorry, but you are quoting ' out of context '. As well as, freely interpreting things, the way you like. I can't help it, if you don't read ' until the end ' of a post: Unless you are able to provide the same ASM routines, optimized ...
- Oct 04, 2018 10:50
- Forum: Beginners
- Topic: Reading a text file into a string array
- Replies: 14
- Views: 365
Dynamic string array definition methods are:
Code: Select all
Dim As String s_arr(Any) '' initialize later (in procedure)
ReDim As String s_arr(1 to 1000) '' with initial size
'' both above are valid, however:
Dim As String s_arr(1 to 1000) '' fixed size (static)
Seems, you've got me the wrong way around.jj2007 wrote:No, I meant a test case for your suggestion to use 32-bit assembly inside 64-bit code.
I meant to state, that this is a: *NO GO* (think of differing ptr sizes e.t.c.).
Ptr (32bit) = 4 Byte -- Ptr (64bit) = 8 Byte (same applies to 'Integer' = derived type).
I'd just call it applied logic.jj2007 wrote:That's an interesting idea.
If you want 64 bit inline ASM ... 64 bit ASM example rotate left/right with a 64 bit registerjj2007 wrote:Can you provide a test case?
(FBC 64, exclusively!).
A hell of a lot simpler, than in 32 bit's ... (no FPU registers needed).
One should distinguish, though, short sequences of inline asm vs subroutines written entirely in asm. Yes, as well as you should start to realize, that 32 bit assembly is only a 'good thing', 'improvement' if used with a 32 bit compiler: FBC 32. With FBC 64, it more than likely, causes a 'slow down...
it's my understanding that fbc compiles itself, and has a c emitter While the compiler itself is written in FB, the included libraries: FB_CRT/FB_GFX2 are written in C. They target different C-compilers (for different builds): FB-DOS uses DJGPP (32 bit only), using GAS emitter Win32 standalone, 32 ...
By Dev I take that to mean Paul Squires but I also ... No, I didn't mean any person, I was referring to the two different 'Job-Descriptions'. A Developer has to deliver code, call it Applications, if you prefer. The main Admin task is, to keep the whole infrastructure 'up and running'. (This includ...
This again clearly shows that Dev's & Admin's are of a very different 'frame of mind': ⋅ Dev's usually want 'bleeding edge' (aka: <latest features>, <experimental>) while, by cons: ⋅ Admin's always prefer 'tried and tested' (aka: <stable>, <secure>) Above is a mutually exclus...
IMO, important to take note of: how the GCC development process is structured ... previous versions (https://www.gnu.org/software/gcc/develop.html) ~~~~~~~~~~~~~~~~~ | | +-- GCC 7 branch created --------+ | \ | v GCC 8 Stage 1 (starts 2017-04-20) GCC 7.1 release (2017-05-02) | \ | v | GCC 7.2 releas...
UNION ARGB_UNION color AS COLORREF TYPE alpha AS UBYTE red AS UBYTE green AS UBYTE blue AS UBYTE END TYPE END UNION COLORREF isn't a FB defined data-type , must be replaced with: ULong ... Then, the UByte's are "top to bottom": Blue (lsb) Green Red Alpha (msb) '' for little endian systems...
@deltarho, it is indeed far simpler code in 64bit ASM, compared to the same in 32bit ASM. Main reason: we can operate straight away with the CPU registers (instead of, having to use FPU registers, just because of required bit-size). Example rotl/rotr (rotate left/right, just 4 lines ASM): Func...
Well, well, who wants DWORD nowadays? We want QWORD , with x64 CPU's & OS's. (FBC 64) A QWORD in the *ALU, saves a lot of pain, while e.g. shifting, rotating e.t.c. (No FPU / SSE needed, for the INT related stuff.) I consider the 32 bit stuff, to be "legacy". (FBC 32) *ALU = arithmetic...
- Sep 26, 2018 11:22
- Forum: Community Discussion
- Replies: 41
- Views: 1655