On Jun 29, 2005, at 07:34, Ralph Lange wrote:
Suggestion:
For V4, make FLNK an array of links with a default size of zero.
The user-defined field would also allow for no default FLNKs at all,
then the user adds as many as needed.
That way you could have nice looking field names:
user_field(convert_units, "MyConversionCalcRecord",
fwd_link_handler);
user_field(determine_output, "MyOutputCalcRecord",
fwd_link_handler);
user_field(write_output, "MyOutputRecord",
fwd_link_handler);
instead of FLNK[0..2].
FLNKs do seem fundamental enough, though,
that I agree with putting them into the base record,
where they might process faster.
One question about processing:
In the current a.FLNK -> b.FLNK -> ... chain,
each individual record's process() routine could decide on its own
as to how it handles the process links.
If b is async, we're waiting until it ends processing
because b decides when to invoke the FLNK.
Will FLNKs[0...N] simply get processed and the originating record
is done, or will it process & wait for completion of FLNK[0],
then proc & wait for FLNK[1], ... ?
-Kay
- Replies:
- Record support and user-defined fields Benjamin Franksen
- References:
- V4 iocRecord: forward linking Ralph Lange
- Navigate by Date:
- Prev:
views Kay-Uwe Kasemir
- Next:
Re: More flexible record scanning Andrew Johnson
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
V4 iocRecord: forward linking Ralph Lange
- Next:
Record support and user-defined fields Benjamin Franksen
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|