symbols | symbols Easy access to commonly-needed symbols | Keyboard library

I've been putting together my own disassembler for Sega Mega Drive ROMs, basing my initial work on the MOTOROLA M68000 FAMILY Programmer’s Reference Manual. Having disassembled a considerable chunk of the ROM, I've attempted to reassemble this disassembled output, using VASM as it can accept the Motorola assembly syntax, using its mot syntax module.

Now, for the vast majority of the reassembly, this has worked well, however there is one wrinkle with operations that have effective addresses defined by the "Program Counter Indirect with Index (8-Bit Displacement) Mode". Given that I'm only now learning Motorola 68000 assembly, I wanted to confirm my understanding and to ask: what is the proper syntax for these operations?

For example, if I have two words:

Given the following identity functions:

There isn't a Genera topic on stackoverflow, but I thought I'd take the chance that one of the (probably) 5 people in the world using it might be here; no harm in trying.

I've run into the situation where a few of the systems I'm working with use pretty printing, which is not implemented on Genera. I've managed to work around the problem in my own system by using the predecessor of pretty printing, XP. Looking at the code in xp-code.lisp and comparing it to that in CCL, it's clear where CCL got its pretty printing functions from.

One solution, now proving inadequate, is to have a top-level eval that does an (xp::install :package my-package) and resume from the redefinition warnings. The problem is that when one of the third-party systems is compiled, they too complain about pretty printing features that are not implemented, so I'd have to install XP in each of these other packages that want pretty printing.

What really needs to happen is for XP to be installed in the common-lisp package, because all of these other systems are going to :use :cl and expect to have a fully functional pretty printing system.

That's not so easy though; the CL package is locked and each XP symbol requires multiple confirms, and a type 'yes', to get it into the CL package. The documentation for External-only Packages and Locking suggests that:

To set up an external-only package, it can be temporarily unlocked and then the desired set of symbols interned in it

but no where does it say how to unlock a package, and the Document Examiner isn't turning up much.

I also have to stop and wonder if I'm barking up the wrong tree. XP was written with Genera in mind, and there are conditionalisations in the code for the platform. It shouldn't be so hard to install using the install function; and I wonder if I'm missing something obvious.

Does anyone out there know how to unlock the CL package, or the proper way install XP in Genera? The included instructions for XP appear to be out of date.

If I navigate to the Build Metadata section for my app within App Store Connect then the Includes Symbols section just says Yes, there is no blue Download dSYM button there.

The XCode build build options Debug Information Format is set to DWARF with dSYM.

So why is there no dSYM on App Store Connect?

This is a React web app. When I run

Somewhere between Java 11 and 17 currency formatting changed to where this:

With the current Rakudo compiler (v2021.10), symbols declared with the ::(…) form do not need to follow the rules for identifiers even when they declare the name of a routine.

This means that the following is code produces the indicated output:

[Editing this question completely] Thank you , for those who helped in building the Periodic Table successfully . As I completed it , I tried to link it with another of my project E-Search , which acts like Google and fetches answers , except that it will fetch me the data of the Periodic Table .

But , I got a problem - not with the searching but with the layout . I'm trying to layout the x-scrollbar in my canvas which will display results regarding the search . However , it is not properly done . Can anyone please help ?

Below here is my code :

This only applies to Visual Studio 2022. I had uninstalled VS2019 and Preview where F# worked absolutely fine (F# 5.0). I am using VS2022 to use F# 6.0 and do not want to go back to F# 5.0.

The issue is specific to F#. I also use C# and I have no issues running the latest C# under VS2022.

There are near continual DevEnv processes running consuming anywhere from 1 to 4 of my CPU's 4 Hyperthreads. I have switched off all experimental options I can find in F# settings.

Sometimes there are 2 or more background processes running , sometimes paused and sometimes none - there appears to be no correlation between this and the background CPU consumption

Sometimes I have a pop up Dialog about waiting to complete an editor process or a compile process.

When devenev.exe is consuming CPU cycles under the properties I see there is always one clr.dllCoUnInitializeEE+0x6790 that is the culprit. I though this was meant to be a short-lived process? Sometimes there are two or three of these consuming most of a HyperThread (There are identical others but with very low or no CPU consumption). The stack on the guilty thread is as follows: