I know it isn't a Vb101 course. I write code all day for work, I am just not sure what you are asking for. If it is
Type Custom
String as String
End Type
change to ;
Type Custom
String to Integer
End Type
based on if it is version 1.11o or not ?
Is this what you are asking to do?
MMud version 1.11o
Re: MMud version 1.11o
I know it isn't a Vb101 course. I write code all day for work, I am just not sure what you are asking for. If it is
Type Custom
String as String
End Type
change to ;
Type Custom
String to Integer
End Type
based on if it is version 1.11o or not ?
Is this what you are asking to do?
example:
----two user defined types defined in a module:
Public TypeA (say for v1.11i through v1.11n)
VarA as Integer
VarB as Integer
VarC(0 to 15) as Integer
End Type
Public TypeB (for v1.11o)
VarA as Integer
VarB as Integer
VarC(0 to 15) as Long
End Type
----and then a global variable that is defined as TypeA:
Global Struct as TypeA
----then all over the program i reference "Struct" like this:
Struct.VarA = 2
Struct.VarC(4) = 23
----it is also passed into subroutines's like:
call sub(varX, Struct, varY)
... the problem is i can't define Struct as TypeA or TypeB at runtime since they are defined within the declarations. the only thing i think i may be able to do (and i just thought of it) is define Struct at the procedure level in each and every function/subroutine that uses it. that would require a lot more code and and a lot of reworkings though as i have module level functions that reference "Struct" as well without having Struct passed to them.
Type Custom
String as String
End Type
change to ;
Type Custom
String to Integer
End Type
based on if it is version 1.11o or not ?
Is this what you are asking to do?
example:
----two user defined types defined in a module:
Public TypeA (say for v1.11i through v1.11n)
VarA as Integer
VarB as Integer
VarC(0 to 15) as Integer
End Type
Public TypeB (for v1.11o)
VarA as Integer
VarB as Integer
VarC(0 to 15) as Long
End Type
----and then a global variable that is defined as TypeA:
Global Struct as TypeA
----then all over the program i reference "Struct" like this:
Struct.VarA = 2
Struct.VarC(4) = 23
----it is also passed into subroutines's like:
call sub(varX, Struct, varY)
... the problem is i can't define Struct as TypeA or TypeB at runtime since they are defined within the declarations. the only thing i think i may be able to do (and i just thought of it) is define Struct at the procedure level in each and every function/subroutine that uses it. that would require a lot more code and and a lot of reworkings though as i have module level functions that reference "Struct" as well without having Struct passed to them.
-
axb9041
Re: MMud version 1.11o
What about;
Type Custom
Version as char
A as Integer
B as Long
End Type
Then something like;
If Custom.Version = o then
'Use Custom.B
Else
'Use Custom.A
just a thought?
Adam
Type Custom
Version as char
A as Integer
B as Long
End Type
Then something like;
If Custom.Version = o then
'Use Custom.B
Else
'Use Custom.A
just a thought?
Adam
Re: MMud version 1.11o
the only thing i think i may be able to do (and i just thought of it) is define Struct at the procedure level in each and every function/subroutine that uses it. that would require a lot more code and and a lot of reworkings though as i have module level functions that reference "Struct" as well without having Struct passed to them.
this actually wont work either because i still have to say, even at the procedure level ...
"Dim X as "
and i can't say
If condition = True then
Dim X as TypeA
Else
Dim X as TypeB
End If
this actually wont work either because i still have to say, even at the procedure level ...
"Dim X as "
and i can't say
If condition = True then
Dim X as TypeA
Else
Dim X as TypeB
End If
Re: MMud version 1.11o
What about;
Type Custom
Version as char
A as Integer
B as Long
End Type
Then something like;
If Custom.Version = o then
'Use Custom.B
Else
'Use Custom.A
just a thought?
Adam
but then before every single line of code that references a "Custom.Element" i have to have an if/then statement which = slow and ugly.
Type Custom
Version as char
A as Integer
B as Long
End Type
Then something like;
If Custom.Version = o then
'Use Custom.B
Else
'Use Custom.A
just a thought?
Adam
but then before every single line of code that references a "Custom.Element" i have to have an if/then statement which = slow and ugly.
-
elpresidente
- Posts: 511
- Joined: Thu Jul 04, 2002 5:00 am
Re: MMud version 1.11o
wouldnt that just be creating two entirly different sub routines that encumpass the entire code?
why not have the two programs and release a frontend with something like
i-n as one button and o+ as another or something like that anyway
why not have the two programs and release a frontend with something like
i-n as one button and o+ as another or something like that anyway
-
axb9041
Re: MMud version 1.11o
After thinking why not just declare it as a long then when saving use CInt to convert it to an integer based on the version? Just treat it as a long throughout the program; but the variable type should only matter when saving. correct?
Re: MMud version 1.11o
After thinking why not just declare it as a long then when saving use CInt to convert it to an integer based on the version? Just treat it as a long throughout the program; but the variable type should only matter when saving. correct?
because there is also 1 added field and the length of each the types matters as well for alignment (a long takes up 4 bytes and a short (int in vb) takes up 2).
because there is also 1 added field and the length of each the types matters as well for alignment (a long takes up 4 bytes and a short (int in vb) takes up 2).
Re: MMud version 1.11o
(v1.44 has been released (http://forumshq.com/showthread.php?t=1450) for support with v1.11o only)