PureBasic Forums - English

You said you wanted the names embedded in the program and I would do that (as others suggest) by putting the data into the DataSection. The minimum storage solution is to use the data directly from the DataSection. How easy access will be depends on how you need to use the data. Here's an example of...

But you can still make 32-bit applications using the latest PellesC compiler.

@RobertSF
Are you using the demo version of PB?

In your ParentCallback function, should the line... ..actually be... The memory failure goes away with this change.

@Little John Thanks for the response... I admit I thought the data.u / data.a WAS the way to get Unicode / Ascii strings in the opposite kind of exe. The data.i @"string" was specifically added some years ago (by Timo I think) but has never showed up in the docs. I agree with your caution ...

Hi Skywalk The project is (probably) quite unusual... A brief synopsis... I have a bunch of programs that manipulate streams of (ASCII) data. The actual nitty-gritty manipulation is done by a collection of (16?) proprietary DLL's. I only have the interfaces to the customer DLL's and they all use ASC...

Well, I have some sympathy for fryquez because it's quite likely that you may need ASCII strings in a Unicode program or Unicode strings in an ASCII program. I certainly do. Using... Data.u "string" Data.a "string" .. is the only way of getting those. I've been using data.a "...

Well, I didn't know PB would create strings in Data with .a and .c. So I learned something new today. I don't suppose this is documented anywhere. (Or is it?) Incidentally, the IMA occurs because *scan is pointing at the string data for "Ascii 1". Using *scan\i[0] interprets the string cha...

I'm really having a bad day. The byte retrieval fails because the version I posted declares i and j as Long. My source (naturally) already has i and j untyped (integer). That should be Integer or defaulted. I owe you several gallons of e-beer to make up for the cr?p. To make sure we have the same so...

Ok - stupid, stupid.

The assembler macro has the line For 64 bit this should (of course) be Because addresses are quads. With that change it works for 64 bit.
I'll go fall on my coding pencil.

Dammit!
There should be a comment line at the top that says.. ; NOTE: 32 bit only
It's in my source file but I guess I chopped it off pasting. I haven't tried 64-bit.

My sincere apologies for that.

I'll try 64-bit and see what's up.

@GPI - you can declare Ascii strings regardless of PB compiler mode if you are prepared to use assembler. My example below shows the use of an assembler macro which creates an Ascii string table in the DataSection. The asm macro creates a table of string addresses followed by the string data (simila...

I'm guessing that you want to be able to send the compiler (in /STANDBY mode) the text of your program in a block of memory.
(and perhaps get results back in memory). Is that correct?

Unfortunately, I admit I don't know of any way to do that.

Have a look at this thread...
http://www.purebasic.fr/english/viewtop ... lliseconds

Well, my 5.50 help file certainly does specify return type.

ElapsedMilliseconds()

Syntax

Result.q = ElapsedMilliseconds()
Description

Returns the number of milliseconds that have elapsed since a specific time in the past.