That would be okay if we didn't have to worry about datatypes. In fact, I have developed a computer language more than 10 years ago that allowed the developer to declare variables without paying any attention to the datatype. The interpreter was smart enough to find out.
Suppose we do: wait window LastName + Age
Then we'll probably get a message like: Operator/operand type mismatch (Error 107)
In fact, the interpreter is merely lazy. Add a little intelligence, and it could easilly write "Johnson23".
>Save the work on the IDE, Peter, and just code like your second example from the start < s >
>
>cheers
>
>
>>[snip]
>>>>Moreover, in that IDE you can switch between views. In one view you only see the descriptors, in another view you also see the technical details like datatype and scope. How about that. Shall we start writing that IDE?
>>>
>>>Not sure what you're trying to say and how valuable this would be.
>>
>>Imagine a button or hotkey that changes the
display of the text, like:
>>
local lcLocalPath, lcBuffer, lnBufferSize, lnResult, lcStructureString
>>
>>lnBufferSize = iif(pcount() = 1, MAX_BUFFER_SIZE, tnBufferSize) + 1
>>lcLocalPath = lcDrive
>>lcBuffer = space(lnBufferSize)
>>lnResult = WNetGetConnection(@lcLocalPath, @lcBuffer, @lnBufferSize)
>>into:
BufferSize = iif(pcount() = 1, MAX_BUFFER_SIZE, BufferSize) + 1
>>LocalPath = Drive
>>Buffer = space(BufferSize)
>>Result = WNetGetConnection(@LocalPath, @Buffer, @BufferSize)
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
