johnm@spudge.UUCP (John Munsch) (09/26/89)
1: I have read that all traces of BCPL are being expunged from AmigaDos 1.4. My question is, does that mean that BPTR's will also go away? If so, then won't a great deal of software break? If not, then what will the average programmer see as being different? 2: Several people said at one time that they had code that would would handle listboxes (not another damn file selector but actual listboxes). If any of those people are going to ever post their code then NOW would be a very good time for me :-) John Munsch | "Llamas are larger than frogs."
ccplumb@rose.waterloo.edu (Colin Plumb) (09/29/89)
In article <3798@spudge.UUCP> johnm@spudge.UUCP (John Munsch) writes: >1: I have read that all traces of BCPL are being expunged from AmigaDos 1.4. >My question is, does that mean that BPTR's will also go away? If so, then >won't a great deal of software break? If not, then what will the average >programmer see as being different? No, the documented interfaces will remain. The change means that the undocumented BCPL-internal interfaces will be going away, so people can patch the dos.library and such without also having to patch the corresponding entry in the BCPL global vector or whatever mess. If you're trying to write a replacement CLI, the fact that all the Commodore-standard utilities are written in BCPL and use magic undocumented BCPL techniques to get their arguments and do everything makes it very difficult. The average programmer will be able to write a replacement CLI that doesn't use Nasty Tricks, SetFuncion() the dos.library just like all the others, and not have to worry about every dos.library call grabbing 1.5 K off the stack and setting up all the address registers with really wierd values. Also, the code should be a lot faster - the BCPL compiler is pretty stupid. -- -Colin