Post reply

Warning - while you were reading a new reply has been posted. You may wish to review your post.
Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Wisp
« on: October 30, 2022, 07:00:54 AM »

Yes, the idea is the interface would be fully compatible with that of WeiDU (or as close as I could reasonably make it). If I ever start making decent progress, I'd be shooting for the roadmap targets and I imagine WeiDU would start moving towards formally being put into maintenance mode.
Posted by: AL|EN
« on: July 11, 2022, 07:54:21 AM »

If I'm reading this correctly, 're-implementation' means API compatibility with the current WeiDU. Can you share your prediction regarding the possible effect of the WeiDU Roadmap, if any?
Posted by: Wisp
« on: May 07, 2022, 06:11:03 PM »

I wouldn't expect that to be a problem. It's already mostly a non-issue, with the 64-bit build of WeiDU.
Posted by: Sam.
« on: April 26, 2022, 05:54:35 AM »

Are you eyeing a particular language?  It would be nice to pick one without a string/buffer size limit.
Posted by: Wisp
« on: April 24, 2022, 02:34:53 AM »

I seem to recall proposing such a scheme, yes, However, the initiative, such as it was, has rather been side-lined by the, perhaps belated, realisation that I'm going to have to high-jack your thread WeiDU is in a rather vulnerable state, technologically. Already WeiDU cannot be compiled with contemporary OCaml and who knows how long it will be until it is no longer straightforward to build old-enough versions of OCaml on contemporary operating systems.

I have slowly come to the realisation that a re-implementation will be necessary, as it would be a very extensive re-write to address the mutable strings, anyway, and if I'm doing major work like that I'd better choose a language that has parallelism. I have begun sketching on a project like that, but it might surprise you to learn I have nothing to show for it, yet.
Posted by: AL|EN
« on: February 27, 2022, 01:59:15 PM »

Hi,


I don't know why I didn't request it earlier but having JSON/other structured data of the entire tp2 and INCLUDE ... files would be wonderful and open a lot of possibilities.


It could for eg: provide the ability to read REQUIRE/FORBBIT etc ... statement and build logic around it, ability to know what tra files are used for current language etc.


Any chances?