|
Hello Anton, >>I can think of absolutely no valid reason to store a pointer to a file. >>When data is in a file it is assumed it is for storage. The next time >>you read the file there is no guarantee that the same data is going to >>be in the location pointed to by the pointer! > And it could be a major security issue! At least Carol Woodbury told us so > at a Rochester Day at common. Obviously they have no chance / it would be a > big effort to check whether the user is authorized to have a pointer at > this object. I am not talking about actually storing a pointer in a database. What I am talking about is using an external definition so that I can do the Prefix keyword. I do not care if the external description is a data file or some totally new entity on the system... Actually the totally new thing sounds better to me, you could make sure someone did not stick anything in there :-) For example say I have a customer object. I need to make a Is_Equal function. In this function I need two references to the same type of object. It would be nice to be able to define these objects externally so that I could make them externally described data structures and base them on a pair of pointers that I pass to the routine. There may be times when I want to reference more than two instances of the object too... (I can not think of any right now but I am sure that if I coded for max of 2 I would find the case where I needed 3 pretty soon thereafter :-) +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.