en en en en en en en en en en en en en en en en en en en en en en en en en en en da en en en en en en en en en en en en en en en en en en en en en en en en en en de en en en en en en en en en en en en en uk en en en es en en en en en en en en en en da en en en en en en de en en de en en en fr en en en en en en en en en pt en en en en en en
By logging into your account, you agree to our Privacy Policy, personal data processing and storage practices as described therein.
Forgot password or user name?
Search in titles only Search in PowerBASIC for Windows only
You are not logged in. You can browse in the PowerBASIC Community, but you must click Login (top right) before you can post. If this is your first visit, check out the FAQ or Sign Up.
All Time Today Last Week Last Month
All Discussions only Photos only Videos only Links only Polls only Events only
Originally posted by Cliff Nichols View Post
So it got me to thinking if there may be some "Mad-Scientist" idea of possibly having a UDT, or some set of functions to fill in a UDT of unknown size and values until runtime??????
Isn't that what XML is for?
24 Jul 2009, 09:17 AM
Originally posted by Cliff Nichols View Post
So it got me to thinking if there may be some "Mad-Scientist" idea of possibly having a UDT, or some set of functions to fill in a UDT of unknown size and values until runtime??????
I'm having a hard time understanding what you mean. Could you describe the situation a little more explicitly?
How would you have a UDT that was unknown in size and values? How would they be unknown "until runtime"?
Are you looking for a "meta-data" UDT that would describe another UDT?
TYPE UDT_DESCRIPTOR_TYPE membername as string * %somelen membertype as string * %somelen memberlength as long END TYPE local MyUDT() as UDT_DESCRIPTOR_TYPE dim MyUDT(1 to 3) MyUDT(1).membername = "StudentFirstName" MyUDT(1).membertype = "string" MyUDT(1).memberlength = 15 MyUDT(2).membername = "StudentLastName" MyUDT(2).membertype = "string" MyUDT(2).memberlength = 25 MyUDT(3).membername = "StudentID" MyUDT(3).membertype = "string" MyUDT(3).memberlength = 8 ...
trying to figure out how you'd use something like that???
TYPE DYNAMIC_UDT_TYPE MyUDT(1).membername AS MyUDT(1).membertype * MyUDT(1).memberlength MyUDT(2).membername AS MyUDT(2).membertype * MyUDT(2).memberlength MyUDT(3).membername AS MyUDT(3).membertype * MyUDT(3).memberlength END TYPE
But I don't think we don't have dynamic TYPE defintions; they have to be defined before compiling...???
Is this more appropriate to a macro????
As I said, I'm a bit unclear on what you're looking for. Any detail you could add would help...
22 Jul 2009, 06:46 PM
GLOBAL MEM ALLOC size TO hMem
Pass 'hMem AS LONG'
Cliff Nichols started a topic Unknown UDT elements
22 Jul 2009, 06:06 PM
Colin got me thinking on UDT's and if you do not know how many elements you may or may not have over to "Passing UDT values to DLLs"
and maybe crossing over to my "Get that DataType"
So it got me to thinking if there may be some "Mad-Scientist" idea of possibly having a UDT, or some set of functions to fill in a UDT of unknown size and values until runtime??????
One idea I had included what I have been told is not only unsupported, but also not advised, but see it in the "Win32Api.inc" is using an array within a UDT (Yes I know...tons of research to do, but its just an idea and even I would not support it till tested, but just grasping at straws that just MIGHT might pan out...if not then nothing lost)
Just for the sake of trying....is it worth trying? or will the 99.9% of you say what I usually do and have ideas why it should not / can not be done?
(Or is it just crazy enough that it might just work????)
Copyright © 1998-2022 PowerBASIC Tools, LLC - All Rights Reserved.
Powered by vBulletin® Version 5.7.0
Copyright © 2022 vBulletin Solutions, Inc. All rights reserved.
All times are GMT-5. This page was generated at 01:35 AM.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, and to analyze site activity. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.