Updated the documentation with some new features and fixes, and updated the main post with a comparision.
local ReplicatedStorage = game:GetService("ReplicatedStorage")
local ClassPP = require(ReplicatedStorage["Class++"])
local class = ClassPP.class
local Car = class "Car" {
Public = {
Brand = "Lamborghini",
},
Private = {
License_Plate = "XXXX"
},
changeLicensePlate = function(self, plate:string)
self.License_Plate = plate
return self
end,
}
local newCar = Car.new()
newCar:changeLicensePlatw(“YYYY”)
can i do it like this?
Oh no, that would give an invalid access specifier error. Members must always be placed inside access specifiers. Try putting the function inside an access specifier, for example, Public like below:
local ReplicatedStorage = game:GetService("ReplicatedStorage")
local ClassPP = require(ReplicatedStorage["Class++"])
local class = ClassPP.class
local Car = class "Car" {
Public = {
Brand = "Lamborghini",
changeLicensePlate = function(self, plate: string) -- We put this function inside the Public Access Specifier, so it can be accessible from everywhere.
self.License_Plate = plate
end,
},
Private = {
License_Plate = "XXXX"
},
}
local newCar = Car.new()
newCar:changeLicensePlate("YYYY")
Check out the documentation for more information access specifiers! You should read the entire thing through, it would be very useful.
Release Beta 1.2.0
- Improved performance on accessing an
object’sPrivateandProtectedaccess specifiers. - Updated the
finalandabstractfunctions to now accept multiple classes with a new syntax. -
Util.inClassScopefunction now accepts a new optionaldefaultLevelvalue that determines the default call stack level the function will start doing the checks on.
A performance comparison picture between 1.1.0 and 1.2.0:
1 Like
Release Beta 1.3.0
- Improved performance when creating and accessing an
object. - Updated the API Reference and Tutorial documentation to include a new feature:
staticmembers.
Introducing a new function:
class.static(accessSpecifier: string, name: string, property: any)
- Classes can now have static members using this function, just like in Java and C++, they belong to the class, and will not replicate to the objects created from the class.
- They’re global, and will be the same everywhere.
- You can access the static members through the class object like:
class.<memberName>.propertyorclass.<memberName>.pfor short.
Check out the documentation for more info!
Release Beta 1.3.1
- Fixed cyclic tables causing stack overflow when the object is getting destroyed.
- Fixed when a member is set to false, that member is no longer indexable.
- Performance improvements.
Make sure to get the latest version to get the most amount of performance, and fixes!
I have put a tool into the .new() function and constructor function, its says This class has no member named “Tool”.
Can you send the script here so I can take a look?
Forgot to include, I’ve updated the API Reference a little bit to show the properties in a better style.
This is the script:
local ReplicatedStorage = game:GetService("ReplicatedStorage")
local CollectionService = game:GetService("CollectionService")
local ClassPP = require(ReplicatedStorage["Class++"])
local class = ClassPP.class
local toolClass = class "Tool" {
constructor = function(self, tool)
if tool and tool:IsA("Tool") then
self.Tool = tool
self.Configuration = require(self.Tool.Config)
self.Tool.Equipped:Connect(function()
self.equipped = true
end)
self.Tool.Unequipped:Connect(function()
self.equipped = false
end)
end
end,
Public = {
equipped = false,
Tool = nil,
Configuration = {},
}
}
CollectionService:GetInstanceAddedSignal("Tool"):Connect(function(tool)
if tool:IsA("Tool") then
local newTool = toolClass.new(tool)
end
end)
This is the Error : {Class++}: This class has no member named "Tool".
I see what you mean now, this is a common mistake that people encounter when creating classes using my module.
This is mostly related on how dictionaries work in Luau, when you set a key to nil, you’re actually removing that key from the table. In this case, the key Tool is being set to nil in the Public access specifier, and since you’re setting the key Tool to nil, Lua automatically removes it from the table, which in the final classData, the Tool member does not exist.
To solve this issue, instead of setting it to nil, you can set it to false.
Here’s your updated code:
local ReplicatedStorage = game:GetService("ReplicatedStorage")
local CollectionService = game:GetService("CollectionService")
local ClassPP = require(ReplicatedStorage["Class++"])
local class = ClassPP.class
local toolClass = class "Tool" {
constructor = function(self, tool)
if tool and tool:IsA("Tool") then
self.Tool = tool
self.Configuration = require(tool.Config)
self.Tool.Equipped:Connect(function()
self.equipped = true
end)
self.Tool.Unequipped:Connect(function()
self.equipped = false
end)
end
end,
Public = {
equipped = false,
Tool = false,
Configuration = {},
}
}
1 Like
Oh man i didnt know this about dictionaries, thank you. 
1 Like
Release Beta 1.4.0
- Performance improvements.
- Fixed some bugs.
- Updated the final method to support functions with the syntax below:
local class, final = ClassPP.class, ClassPP.final
local Test = class "Test" {
Public = {
test = final(function(self, ...)
print(self, ...)
end),
}
}
A performance comparison picture between 1.3.1 and 1.4.0:
2 Likes
Release 1.0.0
Class++ is finally complete and out of beta! I can’t really think of adding any new features, so this is going to be the last version for now.
Until I get a new idea or find an efficient method to implement certain ideas that I currently have, the only updates there will ever be are performance updates and bug fixes. (And maybe some internal changes)
Thanks for using my module!
- Updated the source code to be more efficient and clean, and removed unnecessary comments from the code.
- Updated certain internal functions to be more performant.
- Added a new documentation page describing how to use type checking with Class++. (It’s very useful, check it out!)
- Fixed certain parts of the documentation.
- Removed final functions (using the final keyword with functions), unfortunately implementing final functions required some internal changes that weren’t very worth it for this feature, so I decided to remove it altogether, you can use other methods or just use final classes instead.
(Thefinalkeyword now works as it was in 1.3.1)
If you have any new feature ideas, or found bugs, please don’t hesitate to create a feature request or a bug form though!
2 Likes
Updated the documentation page to give a better explanation on the Type API!
Release 1.0.1
- Members of Friend Access Specifier no longer replicate to the objects as they’re only used within the class object itself.
- Updated the documentation.
1 Like
Release 1.1.0
- Class++ objects now support type checking! This was an update that I was planning to do for a very long time, and it would not have been possible without @HugeCoolboy2007.
- All of the created objects should now have type completion for the members stored in the Public access specifier.
- Creating custom types is no longer needed, however, if you still want to use the full features of type checking in Luau, it’s still recommended that you use custom types for your classes.
- For more info, check out this documentation page.
- Util and Type modules now fully support the
classtype. - Updated the documentation.
(@arbitiu turns out it was possible lol.)
4 Likes
unluckiest timing 
, having released this barely a week ago
1 Like
Well it’s still in beta, so I think I have plenty of time to fix things up, but I didn’t know it would be this broken
My topic was somehow “moderated”, and I was saying that what you made is amazing and very underrated. Probably adding to my list.
2 Likes