|
Hi Rob, The compiler team offcourse knows (that's the benefit of proprietary stuff :-) that a source physical file has the date stored, and does display it. What I was trying to tell is that a SRC-PF is actually a database file and has a structure while this is not the case for an IFS file. Since sources stored in stream files can originate from everywhere, and shared with anybody it isn't that easy to create a standard (IBM doesn't control Notepad as stated earlier) how a source should look like, especially if the underlying storage system doesn't have the possibility to create a structure. BTW, IFS has no structure at all... not even for the maximum characters per line... a line is even something what you consider as separated by CRLF, but Unix people think even different about that... so basically the concept of a 'line' doesn't even exist in an IFS file. Kind regards, Paul -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: dinsdag 3 juni 2003 17:52 To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] Source line change dates - IFS vs source physical files Actually the compiler does put it on the listing. Therefore the editor and the compiler people may have to share a coffee break. Isn't there already a structure in the IFS? After all, you are still limited to so many characters per line. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Paul Nicolay" <Paul.Nicolay@xxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 06/03/2003 10:23 AM Please respond to Websphere Development Studio Client for iSeries To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> cc: Fax to: Subject: Re: [WDSCI-L] Source line change dates - IFS vs source physical files Rob, With source physical files, the date is stored in a seperate field (which is maintained by the editor) which the compiler never reads (he's only interested in the actual coding). With IFS files, this is completely different as they don't have a structure, so neither any place to store the date. This means one would need a convention (for example the first 8 bytes of each line), but this would mean that all editors and compilers should be able to handle this (and when you would edit such an IFS source file with Notepad it definitely doesn't). Just consider yourself spoiled with storing sources in source physical files (ie. database file). Kind regards, Paul ------------------------ Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> wrote: ------------------------ >I wondered if the line change dates were a property of source physical >files, or the property of the editors involved. Your remark seems to >indicate that it is a property of the editor itself. > >That being so, then there is no reason that IBM couldn't fix the fact that >storing source in the IFS doesn't currently support line change dates. > _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
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.