# Using extensions.c in 1.8.0 to Add Packages

Richard Godard (godardr@jsp.umontreal.ca)
Mon, 18 Mar 1996 10:15:39 PST

- Messages sorted by:[ date ][ thread ][ subject ][ author ]

    >> What are the consequences of not updating the Makefile ? I mean since all
    >> the code is included and since the make end linking all the object code ?
    >
    >extension.o may not be rebuilt if dependent files are changed.

    Just delete it, it will force rebuilt... no need to make a 2 page long
    patch :-) :-)

    >> BTW, why not including
    >>
    >> const char *FUP_version = "1.8";
    >>         oklog("        Using File Utilities Package version %s\n",
    >>FUP_version);
    >>
    >> in files.c ?
    >
    >Only because the file.c was delivered this way and I didn't want to
    >modify this file.  The FUP directions tell you to manually put the
    >"FUP_version" constant in version.c and the "oklog()" call into
    >server.c, but I wanted to keep the manual changes localized to the
    >extension.c file.  Hopefully Gustavio will see this coding style and
    >make FUP even more modular.
    >
    >> You call oklog() with an indentation, it will look weird unless you move
    >> that little line in server.c :-)
    >
    >Yes, I was copying from the style I saw in the FUP package.  I'll
    >probably go back to not indenting.

    Well you can simply move a the register_bi_function() line in main in
    server.c to load the bf after displaying STARTING Lambda.....

    >> BTW should you add built-in functions in extlist.c, you will have to change
    >> extensions.c code... which is a lack of modularity :-) :-) :-)
    >
    >Oops <blush>, I didn't notice that the listassoc() and listiassoc()
    >"patch" was already in 1.8.0. Thanks!

    Nope that's not what I mean. I mean that if you add a listslice bf to your
    extlist package, you will also have to change the register_functions in
    extenxion.c

    This would not happend if you define a register_extlist function in
    extlist.c and call this function in extensions.c

    It also allow you to completely change the contents of your extlist.c (like
    the name of the built-in, ...) without needing to change anything in
    extensions.c as long as you keep a register_extlist function in extlist.c

    Hope this help.

    Richard (looking for dynamic loading of bf at startup :-)

    ---
    "640K ought to be enough for anybody."
        -- Bill Gates, 1981