So we keep putting our trust in things that rust
And then we feel the pain of loss
(James, "Stripmining")

Known Bugs, Problems and Limitations

Known bugs

• For missing end-tags, the position of the last occurence of the start-tag with the same name is reported as correspondig start-tag.
• exists() does not work for absolute URIs
• There seems to be a problem with GETSIZE for machines based on CPUs that do not support networking byte order (like those from wIntel).
• I'm still not sure, if GETSIZE for JFIF/JPEG can handle everything correct - but hopefully it does. I've really never seen such an idiotic, braindead, ill-minded and chaoticly structured image-format before.

Known problems (to be fixed)

• Most NEXT and PREV buttons of the docs don't fit; I just wanted to show how to create a navigation bar, but I'm too lazy to maintain it while the structure of the documention isn't fixed.
• As I know myself, these documents still contain loads of typos and ``strange english´´..

Known problems

• URI checking is performed via trying to open a file. As AmigaOS is case-insensitive dealing with filenames, problems might occure when copying the html-object-tree to a case-sensitive filesystem. I recommend to rebuild the whole project at the target system.
• If you specify a <BASE HREF="..">, hsc is unable to find out how the base is related to the destination-directory and will treat all local URIs like external ones; Absolute URIs aren't possible with a base-URI set, of course.
• The obsolete tags <LISTING> and <XMP> might not be treated correctly, as the behavior of these two seems so be not very strickly definded. You should avoid them anyway and use <PRE> or <$source> instead.
• hsc doesn't care much about filenames and their limitations; if, for example, a filename gets too long, it depends on fopen() of your compiler whether an error is reported or the filename is truncated. If you insist on filenames containig 46587643 characters, hsc can cope with it - but your OS probably won't.
• Out-of-memory can cause small memory-leaks. This is because hsc uses a special malloc()-function which just displays an error message and quits using exit(). As hsc keeps track of all allocated resources, it will release everything that could be fully initialised and made it into its supposed resource-list. For out-of-memories during partially initialising complex structures, this failes and can cause memory-leaks (normally approx. 100-500 bytes). Usually, these are handled by your OS or, as for AmigaOS, by the malloc()-function of the run-time-library, so you shouldn't bother too much about that. Blame K&R for their braindamaged memory-managment concepts.
• GetFileSize() probalbly won't work correctly on files greater than 2 GB.
• Until now I couldn't test hsc on some 64-bit OS, so problems might occure if data leave 32-bit address-space.

Limitations

hsc is fully dynamic and it's input size, numer of syntax-elements and etc. is only limited by memory and disk-space. Only some less important status messages are created in classic, braindead zero-terminated C-character-arrays and are truncated if they become too long.

However, for projects larger 500 documents, scanning the project-file on every run takes an awful lot of time; due the lack of any portable concept of keeping data resident after a program exits, there is no workaround for this (same problem like with hsc.prefs); you will have to get rid of the project-file and hscdepp for such projects.