M
medu
Guest
always found misleading the buffer-copy behaviour, it should be either always create the record or expect the record to exists and fail-fast if not... keeping that for backward compatibility only means that there are code that not always behave as expected, very hard to spot the issue and the thing will keep on 'working' till some business user discover there are actually inconsistency in application's data 
best will be if the compiler could issue warnings for cases like that, then at least one knows have potential issues in code and can go and hunt them down... just because is a 4GL doesn't mean it has to be fault-tolerant 
Continue reading...
best will be if the compiler could issue warnings for cases like that, then at least one knows have potential issues in code and can go and hunt them down... just because is a 4GL doesn't mean it has to be fault-tolerant Continue reading...